What's amusing and/or interesting is that the stuff under "Built to Be Written by Agents" also would make it easier to write by hand, I imagine. It's just better debug diagnostics; nothing really to do with agentic development specifically.
Maybe that's just marketing, but it's really intriguing how human best practices are also agent best practices; how, maybe, we've reached a point where even devs aren't recognizing agent best practices as human best practices anymore; and how suddenly best practices are being prioritized in a way they often weren't - humans could/would/were expected to suck it up and deal with poor devex, but agents simply can't. A strange sort of victory for us folks who cared about it.
A friend of mine who works a lot with AI commented that working with AI was making him develop like a grownup for the first time. Turns out that all the best practices really do carry over, but the consequence of not doing it is greater with agents.
On the other hand, Nextjs has been adding debug info that is feasible for agents to parse, but are basically inscrutable to human developers with limited context widows.
It's really "fun" how people suddenly started writing short and concise tutorials on how to use a tool or a library without too much yapping, and somehow instead of being at the beginning of the docs, it's buried deep in "skill.md" file, not intended to be seen by humans.
Remix originally pitched itself as solving the 'middle' layer between frontend and backend. Closing the gap. It never quite managed to do so imo.
Solid's solution here is beautiful. The server RPC and 'live' and 'broadcast' are seamless, and feel much more natural to use than liveview or htmx/datastar imo.
Still waiting for Vue 3.6 Vapor to be released which is supposed to be more competitive with these frameworks like Svelte and Solid in performance. Vue 3.5 came out in Sept 2024 and I've ported a lot of code off Vue since then.
Imagine people believing morality and acting on it?!
I literally did, for a bunch of my projects and the ones of clients. A friend even did it for a pretty big brand that had a juicy Vercel bill. Burn in hell Guillermo
I see something like ”const user = createMemo(() => fetchUser(props.id));” or “use server” and I’m instantly reminded of why I abandoned JS frameworks (not to mention anything touching JS on the server).
I much prefer Solid over React, but at least the idea of a compiler makes so much more sense instead of manually maintaining memoization.
The async graph is VERY cool. It does a great job of encapsulating async's nature to cause "colored" functions by using the existing signal graph (which admittedly is its own color; but virtually every UI framework has similar coloring so at least Solid's cutting a color/making it composable).
Contrast that with React, where hooks are colored functions. You thought that hooks were just functions? Nope, if you have a hook, it MUST be called in a hook/component... exactly like async. Did you want to load this TTS player conditionally? Hahah, you can't. Have fun allocating memory for every TTS provider your app supports, even if the user uses only 1 player. https://news.ycombinator.com/item?id=45257413
"Thanks to async in the graph we can detect waterfalls, poorly constructed effect loops, poorly scaling graph shapes like wide graph fanouts and fan-ins." Incredibly cool. Apparently Tanstack Query has a waterfall detector https://github.com/bamlab/tanstack-query-detect-waterfall so the other frameworks have something similar, but it won't work with their state graphs.
I honestly don't remember what drove me (and apparently a lot of the frontend JS community) to place my bets on Svelte over Solid, years ago now. It probably had something to do with Svelte feeling (and at the time, being) much simpler to develop in, looking on the surface like simple HTML and CSS with some JavaScript sprinkled in, and believing strongly in its magic compiler.
Honestly, I was probably just so tired of React that it felt refreshing to develop in something so un-React-like, and it ergonomically felt better at the time than writing something similar to React via Solid, even if the latter was still holding its own in performance on paper. If you've spent years learning French then it might feel more refreshing to start learning Japanese than Italian.
It turns out Solid had a lot of it right all along. And after using Svelte for a while, something starting feeling... weird. For all its complexity, something I always appreciated about React was that I was ultimately just writing JavaScript, and with Svelte it felt like I was writing in something only made to resemble JavaScript.
I still really appreciate Svelte, but I'm wondering if this would be a good time to see if Solid will feel more "natural" to me, having worked with JavaScript all these years. Curious if anyone can confirm if that would be the case.
Now might also be a good time to tinker with it myself before the coding models are fully up to date on 2.0 and I turn to laziness (/efficiency) and have them handle the rest.
I also remember caring about frameworks, and having long debates on HN about what was better. Haven't cared or done that in quite awhile now. It's be like debating low level assembly instructions. We just no longer work at that level.
I was in same position, but I picked Svelte because I really liked the older syntax. `$: derived` values, everything reactive, etc. But post Svelte 5, even though I get the why - it's so similar to other libs like React and Solid that Solid makes more sense for me now.
I used Svelte extensively since v3 but ended up switching to Solid this year. I just want to be able to write TS/TSX without needing any extra tooling around it.
Solid is just JSX which is stock typescript tooling.
* Does not need any unique editor plugin like Svelte and Vue to provide a language server.
* Worked with Tsgo day 1.
* Works with oxfmt by default day 1.
* Works somewhat with oxlint out of the box day 1, eslint plugin is fully supported.
Svelte has a much more complicated build system and customised plugins that need regular upkeep, for basic usage it might just look like a vite plugin line and the eslint/prettier config that gets generated as part of project init but as your app grows and you maintain it longer term you absolutely start feeling the deficiencies and weight of all the svelte tooling.
Solid has a compiler and an eslint plugin, but otherwise leverages the standard typescript tooling, it's so much faster. Ryan's looking at reactive script now but it was an extremely good decision to not take on the tooling maintenance of Svelte and Vue.
"Built to be written by agents"? To me that would mean to drop the framework altogether: they've always just been an abstraction to bridge knowledge gaps in bigger teams and enforce coding patterns. But now that's just the job of the agents, and instead you can prompt it to set up a proper server in any language you want.
I'm working on something right now it's called ReactiveScript which takes Solid's constraints and makes them in the compiled language. Its still WIP but early results are promising. It can do better than vanillaJS because async bugs are compiler error by construction etc. It's a bit like the Rust mentality. If the agent can't write bad code if it won't compile.
I think we will see more of this. Frameworks have been "languages" for years. Rich Harris of Svelte saw that. This is exactly the remaining gap right now. Peeling away the layers is also peeling away the guard rails. You can add those back with rigor of testing. But huge benefits to just encoding our learnings in the language itself.
You've always been able to early return in Solid it just was never going to do what you expected because components run once. That's not something to fix. A language can look at `if` and say that's a `<Show>` component, but effectively its wrapping the choice in the templating(reactive expression). It doesn't really matter because those templates run once too so nesting is fine. But ultimately supporting it is supporting sugar not much else.
You could say that about some libraries, but LLMs haven't made reactive frameworks obsolete; on the contrary, they're very effective at using them, and they write better, more maintainable, and more consistent code with them than when they try to hand-write JS that renders to the DOM. Anything that can "bridge knowledge gaps in bigger teams and enforce coding patterns" can also help write code with agents!
If anything, I think attention limits, token costs, and declining performance as size/complexity increase means good abstractions are more necessary than ever.
What's amusing and/or interesting is that the stuff under "Built to Be Written by Agents" also would make it easier to write by hand, I imagine. It's just better debug diagnostics; nothing really to do with agentic development specifically.
Maybe that's just marketing, but it's really intriguing how human best practices are also agent best practices; how, maybe, we've reached a point where even devs aren't recognizing agent best practices as human best practices anymore; and how suddenly best practices are being prioritized in a way they often weren't - humans could/would/were expected to suck it up and deal with poor devex, but agents simply can't. A strange sort of victory for us folks who cared about it.
A friend of mine who works a lot with AI commented that working with AI was making him develop like a grownup for the first time. Turns out that all the best practices really do carry over, but the consequence of not doing it is greater with agents.
Kind of the same reason Rust works very well with agents, good error messages and strict type system. Harder to screw up for humans and bots alike.
If only Rust had compile times of Go. I often find myself with multiple agents stalling, all waiting for the cargo lock.
Try C# as a middle ground. Compiles faster than Rust, runs faster than Go
On the other hand, Nextjs has been adding debug info that is feasible for agents to parse, but are basically inscrutable to human developers with limited context widows.
It's really "fun" how people suddenly started writing short and concise tutorials on how to use a tool or a library without too much yapping, and somehow instead of being at the beginning of the docs, it's buried deep in "skill.md" file, not intended to be seen by humans.
Remix originally pitched itself as solving the 'middle' layer between frontend and backend. Closing the gap. It never quite managed to do so imo.
Solid's solution here is beautiful. The server RPC and 'live' and 'broadcast' are seamless, and feel much more natural to use than liveview or htmx/datastar imo.
Still waiting for Vue 3.6 Vapor to be released which is supposed to be more competitive with these frameworks like Svelte and Solid in performance. Vue 3.5 came out in Sept 2024 and I've ported a lot of code off Vue since then.
Performance of Vapor mode is similar to Solid and Svelte.
https://krausest.github.io/js-framework-benchmark/current.ht...
Between Solid, Vue, and Svelte it's more a matter of features and personal preference than performance at this point.
There are still not many component libraries for Solid. But if I needed to build something from scratch, I would definitely try Solid.
It just feels like the right way React should be.
I disagree.
Vercel's UI SDK just launched with Solid support.
Theres also Kobalte, Ark UI, Park UI, Solid UI, Shadcn Solid, Corvu, Material Design Solid, and more.
Who’s still using Vercel after they met with Netanyahu..???
Imagine people scrambling to migrate away from their nextjs or react codebases, because Guillermo Rauch met with Netanyahu...
Imagine people believing morality and acting on it?!
I literally did, for a bunch of my projects and the ones of clients. A friend even did it for a pretty big brand that had a juicy Vercel bill. Burn in hell Guillermo
Who's still voting Trump after he met with Netanyahu..???
I'm being facetious, but what would you expect?
These days are component libraries even necessary
Of course, if you want two applications to look the same.
That's a design system. You can make that for your own apps yourself.
not only look the same, but perhaps even more importantly, behave the same.
"make these two applications look the same" works surprisingly well.
Congrats to the Solid team. This is a monumental release.
I see something like ”const user = createMemo(() => fetchUser(props.id));” or “use server” and I’m instantly reminded of why I abandoned JS frameworks (not to mention anything touching JS on the server).
I much prefer Solid over React, but at least the idea of a compiler makes so much more sense instead of manually maintaining memoization.
Hoping the TanStack Solid 2 adapters are out soon. They're the only blockers for me now.
The async graph is VERY cool. It does a great job of encapsulating async's nature to cause "colored" functions by using the existing signal graph (which admittedly is its own color; but virtually every UI framework has similar coloring so at least Solid's cutting a color/making it composable).
Contrast that with React, where hooks are colored functions. You thought that hooks were just functions? Nope, if you have a hook, it MUST be called in a hook/component... exactly like async. Did you want to load this TTS player conditionally? Hahah, you can't. Have fun allocating memory for every TTS provider your app supports, even if the user uses only 1 player. https://news.ycombinator.com/item?id=45257413
"Thanks to async in the graph we can detect waterfalls, poorly constructed effect loops, poorly scaling graph shapes like wide graph fanouts and fan-ins." Incredibly cool. Apparently Tanstack Query has a waterfall detector https://github.com/bamlab/tanstack-query-detect-waterfall so the other frameworks have something similar, but it won't work with their state graphs.
> Did you want to load this TTS player conditionally? Hahah, you can't.
Um, you can? Just change this:
to this:I honestly don't remember what drove me (and apparently a lot of the frontend JS community) to place my bets on Svelte over Solid, years ago now. It probably had something to do with Svelte feeling (and at the time, being) much simpler to develop in, looking on the surface like simple HTML and CSS with some JavaScript sprinkled in, and believing strongly in its magic compiler.
Honestly, I was probably just so tired of React that it felt refreshing to develop in something so un-React-like, and it ergonomically felt better at the time than writing something similar to React via Solid, even if the latter was still holding its own in performance on paper. If you've spent years learning French then it might feel more refreshing to start learning Japanese than Italian.
It turns out Solid had a lot of it right all along. And after using Svelte for a while, something starting feeling... weird. For all its complexity, something I always appreciated about React was that I was ultimately just writing JavaScript, and with Svelte it felt like I was writing in something only made to resemble JavaScript.
I still really appreciate Svelte, but I'm wondering if this would be a good time to see if Solid will feel more "natural" to me, having worked with JavaScript all these years. Curious if anyone can confirm if that would be the case.
Now might also be a good time to tinker with it myself before the coding models are fully up to date on 2.0 and I turn to laziness (/efficiency) and have them handle the rest.
I also remember caring about frameworks, and having long debates on HN about what was better. Haven't cared or done that in quite awhile now. It's be like debating low level assembly instructions. We just no longer work at that level.
I was in same position, but I picked Svelte because I really liked the older syntax. `$: derived` values, everything reactive, etc. But post Svelte 5, even though I get the why - it's so similar to other libs like React and Solid that Solid makes more sense for me now.
I used Svelte extensively since v3 but ended up switching to Solid this year. I just want to be able to write TS/TSX without needing any extra tooling around it.
What do you mean by extra tooling? It's just a basic Vite setup.
Solid is just JSX which is stock typescript tooling.
* Does not need any unique editor plugin like Svelte and Vue to provide a language server.
* Worked with Tsgo day 1.
* Works with oxfmt by default day 1.
* Works somewhat with oxlint out of the box day 1, eslint plugin is fully supported.
Svelte has a much more complicated build system and customised plugins that need regular upkeep, for basic usage it might just look like a vite plugin line and the eslint/prettier config that gets generated as part of project init but as your app grows and you maintain it longer term you absolutely start feeling the deficiencies and weight of all the svelte tooling.
Solid has a compiler and an eslint plugin, but otherwise leverages the standard typescript tooling, it's so much faster. Ryan's looking at reactive script now but it was an extremely good decision to not take on the tooling maintenance of Svelte and Vue.
Is it? I thought it had its own special compiler, too.
You're probably using a lot more than that to write Svelte.
Solid has been my framework of choice for the past 5 years. Haven't touched React since.
They've gone all in on AI and Agents, how wonderful
Hurray! Solid 2.0 is finally out!
"Built to be written by agents"? To me that would mean to drop the framework altogether: they've always just been an abstraction to bridge knowledge gaps in bigger teams and enforce coding patterns. But now that's just the job of the agents, and instead you can prompt it to set up a proper server in any language you want.
I'm working on something right now it's called ReactiveScript which takes Solid's constraints and makes them in the compiled language. Its still WIP but early results are promising. It can do better than vanillaJS because async bugs are compiler error by construction etc. It's a bit like the Rust mentality. If the agent can't write bad code if it won't compile.
I think we will see more of this. Frameworks have been "languages" for years. Rich Harris of Svelte saw that. This is exactly the remaining gap right now. Peeling away the layers is also peeling away the guard rails. You can add those back with rigor of testing. But huge benefits to just encoding our learnings in the language itself.
Hey random question, does Solid these days have anything that lets you early return? I haven't looked into that in a while
You've always been able to early return in Solid it just was never going to do what you expected because components run once. That's not something to fix. A language can look at `if` and say that's a `<Show>` component, but effectively its wrapping the choice in the templating(reactive expression). It doesn't really matter because those templates run once too so nesting is fine. But ultimately supporting it is supporting sugar not much else.
Most used of early return can be replaced with Solid's <Show>
You could say that about some libraries, but LLMs haven't made reactive frameworks obsolete; on the contrary, they're very effective at using them, and they write better, more maintainable, and more consistent code with them than when they try to hand-write JS that renders to the DOM. Anything that can "bridge knowledge gaps in bigger teams and enforce coding patterns" can also help write code with agents!
That's certainly been my experience, agents perform better in well maintained code bases with obvious architectural patterns reinforced by frameworks.
How do you keep code well-maintained when agents are generating so much code nowadays? Have agents code review the agents?
It’s November 2026. I haven’t written more than 2 lines of code in a day since January 2026.
So if a framework is made so that coding agents can use it well, why is it a negative?
I’m not going to be writing SolidJS by hand.
If anything, I think attention limits, token costs, and declining performance as size/complexity increase means good abstractions are more necessary than ever.
Ask Claude to write a SaaS landing page for you in React/Next.js
Then ask Claude to write a SaaS landing page for you in assembly.
Then compare the results.
So you want knowledge gaps between agents and the team.