Solid 2.0

(solidjs.com)

46 points | by pier25 55 minutes ago

5 comments

  • ale 18 minutes 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 6 minutes 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!
    • aurareturn 11 minutes 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.

    • croes 9 minutes ago
      So you want knowledge gaps between agents and the team.
  • maxloh 21 minutes 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.

    • dbbk 8 minutes ago
      These days are component libraries even necessary
      • robertlagrant 5 minutes ago
        Of course, if you want two applications to look the same.
  • _nothing 5 minutes 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.

  • pier25 41 minutes ago
    Congrats to the Solid team. This is a monumental release.
  • ishritmadaan 45 minutes ago
    Hurray! Solid 2.0 is finally out!