I've been pretty much on this side of the argument. When I've seen the work that goes into designing a framework even one that I generally have little love for like Next.js, but still appalled by things like vinext. Atleast there I get the platform tension. But a library or tool
What Theo is doing here is actively harmful for OSS maintainers. This behavior just causes people to say "if this guy can do X why can't you do Y". But vibed rewrites are completely useless unless you plan to support them.
It's known that @solid_js already has a very performant, very strict runtime. @devagrawal09 asks what if you could do more ahead of time, because lets face it you aren't writing the code anyway?
Ugly as sin, but super powered for agents?
Introducing solid-yield
A Solid 2.0 library that provides fully type-safe reactivity, async, error, and context handling
At the cost of slightly more verbose code, you get strict compile time checks for your code. No missed boundaries and providers.
github.com/devagrawal09/s…
Nah. Frontend is far from dead. Huge movement still happening in the space at rapid rate. People are discussing it less mostly because discussion on frontend has been trending superficial for years. "What syntax do you prefer?" "How did Vercel/React ruin things today?"
I didn't get in on the conversation as to not invite more work for myself, but AI has been great for PRs and issues. Yes some things are clearly exhaustive for no real reason, but we have people contributing now that never would have before. People who take place in the