Solid 2.0

(solidjs.com)

101 points | by pier25 1 hour ago

7 comments

  • wk_end 27 minutes 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.

  • pwmglenn 40 minutes 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 1 hour ago
    Congrats to the Solid team. This is a monumental release.
  • maxloh 1 hour 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 1 hour 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 32 minutes ago
        Who’s still using Vercel after they met with Netanyahu..???
    • dbbk 1 hour ago
      These days are component libraries even necessary
      • robertlagrant 1 hour ago
        Of course, if you want two applications to look the same.
        • squidsoup 1 hour ago
          not only look the same, but perhaps even more importantly, behave the same.
  • _nothing 1 hour 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 11 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 50 minutes 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 42 minutes ago
        What do you mean by extra tooling? It's just a basic Vite setup.
        • pier25 30 minutes ago
          You're probably using a lot more than that to write Svelte.
  • ishritmadaan 1 hour ago
    Hurray! Solid 2.0 is finally out!
  • ale 1 hour 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.
    • rafram 1 hour 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 1 hour ago
        That's certainly been my experience, agents perform better in well maintained code bases with obvious architectural patterns reinforced by frameworks.
    • aurareturn 1 hour 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 48 minutes ago
      If anything, I think attention limits, token costs, and declining performance as size/complexity increase means good abstractions are more necessary than ever.
    • croes 1 hour ago
      So you want knowledge gaps between agents and the team.
    • kube-system 51 minutes 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.