NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
▲Solid 2.0 (solidjs.com)
wk_end 1 hours ago [-]
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.

novacrazy 35 minutes ago [-]
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.
snordgren 19 minutes ago [-]
If only Rust had compile times of Go. I often find myself with multiple agents stalling, all waiting for the cargo lock.
Bolwin 6 minutes ago [-]
Try C# as a middle ground. Compiles faster than Rust, runs faster than Go
pwmglenn 1 hours ago [-]
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.

pier25 2 hours ago [-]
Congrats to the Solid team. This is a monumental release.
maxloh 2 hours ago [-]
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.

pwmglenn 2 hours ago [-]
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.

salah7252 1 hours ago [-]
Who’s still using Vercel after they met with Netanyahu..???
22 minutes ago [-]
giveaccountpls 29 minutes ago [-]
Who's still voting Trump after he met with Netanyahu..???

I'm being facetious, but what would you expect?

azangru 18 minutes ago [-]
Imagine people scrambling to migrate away from their nextjs or react codebases, because Guillermo Rauch met with Netanyahu...
dbbk 2 hours ago [-]
These days are component libraries even necessary
robertlagrant 2 hours ago [-]
Of course, if you want two applications to look the same.
latchkey 15 minutes ago [-]
"make these two applications look the same" works surprisingly well.
squidsoup 2 hours ago [-]
not only look the same, but perhaps even more importantly, behave the same.
otherflavors 12 minutes ago [-]
They've gone all in on AI and Agents, how wonderful
_nothing 2 hours ago [-]
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.

bottlepalm 55 minutes ago [-]
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.
pier25 2 hours ago [-]
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.
tancop 1 hours ago [-]
What do you mean by extra tooling? It's just a basic Vite setup.
pier25 1 hours ago [-]
You're probably using a lot more than that to write Svelte.
ishritmadaan 3 hours ago [-]
Hurray! Solid 2.0 is finally out!
ale 2 hours ago [-]
"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.
ryansolid 30 minutes ago [-]
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.

rafram 2 hours ago [-]
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!
squidsoup 2 hours ago [-]
That's certainly been my experience, agents perform better in well maintained code bases with obvious architectural patterns reinforced by frameworks.
jaapz 12 minutes ago [-]
How do you keep code well-maintained when agents are generating so much code nowadays? Have agents code review the agents?
aurareturn 2 hours ago [-]
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.

wpietri 2 hours ago [-]
If anything, I think attention limits, token costs, and declining performance as size/complexity increase means good abstractions are more necessary than ever.
kube-system 2 hours ago [-]
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.

croes 2 hours ago [-]
So you want knowledge gaps between agents and the team.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 21:38:33 GMT+0000 (Coordinated Universal Time) with Vercel.