Flarette

[Flarette @solar_flarette]

@mitchellh what's up with corner snapping?

[Flarette @solar_flarette]

@choblin29 I don't think they are using fable it would be too expensive it's opus and you can already use it.

[Flarette @solar_flarette]

@CampbellKaleb23 Today is the last day of the banked reset anthropic gave at Opus 5.5 launch so everyone tries to burn usage before it expires

[Flarette @solar_flarette]

@housecor Lots of people want to know what's currently being asked on the interviews. Knowing AI can land you a better job. This is just the current reality. maybe when AI is more mature people will spare more time for other stuff but right now AI knowledge is sparse and unstructured

[Flarette @solar_flarette]

@rauchg If only there was a country with .js domain, they would have rivaled America on the domain royalties alone.

[Flarette @solar_flarette]

@DavidKPiano How is this different from having workflow skill with links to the stages that agent opens lazily? From my experience router skills hold extremely well in context without having to turn it into code.

[Flarette @solar_flarette]

@DavidKPiano Literally everone has a gemeni on their phone and i expect browsers will have one as well soon. This is a problem for platforms to solve. Why pay 10$ to use agent in your app when user can pay $20 and use it everywhere. Economy of scale will absorb this model and app devs follow.

[Flarette @solar_flarette]

@noahreeveshq My workflow skill says to delete memories after finishing the task. Memories are transient knowlage about state of the work in progress. Leftover memories really are the worst poison.

[Flarette @solar_flarette]

@badlogicgames "Don't worry! this time - we start from scratch "

[Flarette @solar_flarette]

@erkamyaman_ng @Enea_Jahollari Tsrx

[Flarette @solar_flarette]

@saltyAom Platforms move so fast these days. The library you start writing 5 months ago is already legacy at the release. 😭

[Flarette @solar_flarette]

In light of recent bun fork of oxc/oxfmt - Let's assume it's done. "Revenue split across deps" would it not incentivese to refactor out all deps from of your package leading to the ecosystem fragmentation and killing low level and primitive deps completely? There is now new incentive to increase your percentage sharing the bundle. Every bundle going zero depths by forking and incorporating snapshot of other packages and we end up with the same unmaintainable low quality buggy code just encapsulated by the final all-in-one framework with maintainer's trust me bro stump of quality even though they were not responsible for those dependencies before and likely won't focus on maintaing them. Even worse, once payment is implemented it will damage motivation even more than just not getting downloads - why do anything just so others profit off you. I'm not arguing against compensation but the solution in this shape will only benefit big players.

[Flarette @solar_flarette]

@fuma_nama Not Elysia?

[Flarette @solar_flarette]

@saltyAom

[Flarette @solar_flarette]

@saltyAom Does it work with better-result error types?

[awg @aawoogie]

Finally drawing gemini :3

[Flarette @solar_flarette]

@alexdotjs @EffectTS_ rxjs with extra steps but worse. It's so funny.

[Flarette @solar_flarette]

@HakureiRyan @saltyAom It's mirrored, look at the screen

[Flarette @solar_flarette]

@lsn_al_ghb @trq212 Because given the budget you would rather have a team of experts or a team of generalists? The comparison only holds one to one but in group project multiple experts cooperating would beat generallists who would still need to separate roles just at lower starting point.