Solid 2.0

365 points by pier25 23 hours ago on hackernews | 114 comments

ishritmadaan | 23 hours ago

Hurray! Solid 2.0 is finally out!

[OP] pier25 | 23 hours ago

Congrats to the Solid team. This is a monumental release.

maxloh | 23 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.

These days are component libraries even necessary

robertlagrant | 23 hours ago

Of course, if you want two applications to look the same.

squidsoup | 22 hours ago

not only look the same, but perhaps even more importantly, behave the same.

latchkey | 21 hours ago

"make these two applications look the same" works surprisingly well.
That's a design system. You can make that for your own apps yourself.

skrebbel | 12 hours ago

The worst thing about AI is super inexperienced devs doing hot takes like these.
I have 20 years of experience.

pwmglenn | 22 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 | 22 hours ago

Who’s still using Vercel after they met with Netanyahu..???

giveaccountpls | 21 hours ago

Who's still voting Trump after he met with Netanyahu..???

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

azangru | 21 hours ago

Imagine people scrambling to migrate away from their nextjs or react codebases, because Guillermo Rauch met with Netanyahu...

gr__or | 19 hours ago

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

tommica | 12 hours ago

> Burn in hell Guillermo

That is a bit of an over-reaction.

I don't think so.
You are being downvoted, but I surely don't want to be in any way associated with a genocidal monster, so your question is valid.
What exactly does UI SDK do? The site doesn't make it clear.

Appreciate the the other examples though.

kilburn | 11 hours ago

Vercel UI SDK is a "headless" UI tooklit. "Headless UI" is packaging of behavior that has to be implemented in javascript to get properly working widgets.

For instance, to implement a menu you have to support things like keyboard navigation and auto-closing when the user clicks elsewhere.

Gettings these sort of behaviors right across all browsers is oftentimes _hard_, and testing them properly is very time consuming. That's why it's useful to have it built and tested by a large company.

Traditionally, these behaviors came built-in with your "UI Widget Library" of choice (e.g., https://ant.design/). However, widget libraries bring in their own style and subtle opinions. When you are aligned with those everything is great, but when you want to deviate visually or behaviorally then you have a hard time.

In contrast, "headless UI" packages these behaviors (and only the behaviors) as little snippets that you "plug in" to your own widgets/components. Since how these behaviors get to be "plugged in" to components and how they can interact between them may be dictated by the UI framework/library (e.g., react, astro, solid) the headless ui kits explicitly call those that they support.

For Vercel UI SDK specifically, you can check the list of behaviors they implement here https://ui-sdk.dev/docs/core/behaviors

kalualualeiamba | 19 hours ago

Dependency management inside components is much saner that's for sure.
"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.

aurareturn | 23 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.

conartist6 | 16 hours ago

What a pisser

croes | 23 hours ago

So you want knowledge gaps between agents and the team.

rafram | 23 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 | 22 hours ago

That's certainly been my experience, agents perform better in well maintained code bases with obvious architectural patterns reinforced by frameworks.

jaapz | 21 hours ago

How do you keep code well-maintained when agents are generating so much code nowadays? Have agents code review the agents?

kube-system | 22 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.

wpietri | 22 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.
Token costs are extremely important, and a big factor in any front-end/server tooling I end up picking nowadays.

I'll gladly sacrifice 20%-30% of features of one thing over another if it lets me use that much fewer tokens.

ryansolid | 21 hours 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.

nvme0n1p1 | 20 hours ago

Hey random question, does Solid these days have anything that lets you early return? I haven't looked into that in a while

thomastill | 20 hours ago

Most used of early return can be replaced with Solid's <Show>

ryansolid | 19 hours ago

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.

nvme0n1p1 | 2 hours ago

> it just was never going to do what you expected

Yeah that's what I mean.

A lot of my react components start out with the equivalent of

  if (state==error) return <p>error</p>;
  if (state==loading) return <p>loading</p>;
  if (!connection) return <p>offline</p>;
  if (admin) return <Redirect/>;
doing that with <Show /> (and passing the function so TypeScript still works) means the conditions take 20 lines instead of 4, and the meat of my component is indented an extra 8 levels.
Makes sense, Signal dependency graphs can also be more easily debugged/visualuzed with a compiler in a way that does not require manual labeling. I did this with a toy compiler I built that's just a subset of Typescript with a new reactive variable operator (which personally i find to be the most sensible approach for a frontend DSL). Not sure what you mean by guards rails though, the Rust compile check mentality is exactly the type of pampering that the webdev community likes.
this keeps getting told but are there examples of great software written by agents without frameworks?

_nothing | 23 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.

[OP] pier25 | 22 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 | 22 hours ago

What do you mean by extra tooling? It's just a basic Vite setup.

[OP] pier25 | 22 hours ago

You're probably using a lot more than that to write Svelte.

DimmieMan | 20 hours ago

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.

christophilus | 19 hours ago

Is it? I thought it had its own special compiler, too.

[OP] pier25 | 15 hours ago

you do need a compiler but the parent comment refers to the tooling when writing solid in your editor or IDE

MrJohz | 14 hours ago

It does, but it's not needed for static analysis at all. From an IDE's perspective, SolidJS is just completely normal JSX expressions, which it can usually already handle.

bottlepalm | 22 hours 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.
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.

pwmglenn | 22 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.

ricardobeat | 20 hours ago

`broadcast` is not mentioned in the release, so I went looking for it in the docs and was hit in the face with slop:

> Declares a live server function whose answer is the same for every viewer: on the client exactly live(fn) — the sharing is the server's.

> See Share one live answer across viewers for what is shared, what runs per caller, and the compile-time capture rule.

> live() runs one producer per connection, which is right when the answer can depend on who is asking.

Incredible, not even a Claudish linguistics expert could make sense of this. This is advanced slop

skew-aberration | 13 hours ago

It's terse but I can make sense of this. I read it as broadcast() wrapping a single live() somehow, because invoking live() per a connection on the server would lead to viewers (clients? callers?) potentially seeing different streams.

weego | 7 hours ago

Broadcast are async functions that will hydrate in the client after render.

Broadcast is one result to many Live is many results to many

conartist6 | 9 hours ago

I made the mistake of reading the signals code.

Nearly horfed right on my laptop. I won't be using that slop fest.

0xblinq | 19 hours ago

Remix (and React router, and the folks behind it) pitch a different thing each week, and they never manage to do it because they change their mind every Tuesday.

wk_end | 22 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 | 21 hours 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 | 21 hours ago

If only Rust had compile times of Go. I often find myself with multiple agents stalling, all waiting for the cargo lock.

Bolwin | 21 hours ago

Try C# as a middle ground. Compiles faster than Rust, runs faster than Go

[OP] pier25 | 15 hours ago

C# and the CLR are great but the ecosystem is pretty much non existent outside of .NET

melodyogonna | 9 hours ago

> Runs faster than Go

Citation is needed

mihaelm | 19 hours ago

The way Rust compile times can sneak up on you as your project grows is not to be underestimated. More so if you're running multiple agents in parallel.

But frankly I don't mind it as much with agents as I did when handwriting the code. It's on the agent to endure the slower feedback loop.

nextaccountic | 18 hours ago

waiting for the cargo lock is something else: cargo was not designed for multiple simultaneous entities developing in parallel

my take is, in the current state of the ecosystem, you should use https://github.com/kunobi-ninja/kache and make agente work on separate worktrees,each with their own target directory

usually separate target dirs means multi-gigabyte artifacts for each worktrees (and waiting for the same code to compile again). but not with kache, it builds only once and reduplicate files (with reflinks if your filesystem supports it)

there's also some projects for live reloading rust, and some specific tips about faster builds during iterative development (the most relevant being, use the mold linker)

supermatt | 9 hours ago

Thanks. I have been using CoW for this but will see how kache compares.

obeavs | 15 hours ago

Youre looking for Moonbit

phplovesong | 10 hours ago

There is Lisette, thats basically Rust for Go. Been amazing for our team, we are rewriting a legacy system in Lisette. So far so good!

lemming | 21 hours ago

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.

gwerbin | 15 hours ago

Same here, bigtime.

AI has forced me to write out more planning documents. Not waterfall strategic planning, but tactical planning such as describing the desired behavior of a script before I write it, or pre-registering a data analysis and my expected findings in writing before I start querying data -- that goes in a PLAN.md within whatever folder I'm working on at the moment.

I now keep a systematic todo list that I call TASKS.md, which groups tasks into topical sections and every task has an ID, such as MD3 or EV7.

I also keep an append-only-ish journal of results, findings, unfinished thoughts, rejected ideas, etc.

All of that goes right into my project Git repo. It works great for both AI agents and humans.

But perhaps more interesting than my new workflows, is that I actually learn things from the AI. The idea to start pre-registering all my little analyses, not just the big tasks, was a Claude-ism that I've since adopted even when I'm not using AI.

hdjrudni | 9 hours ago

I do TODO.md instead of TASKS.md but what's the benefit of giving each task an ID? Just easier for you to refer to a specific task? I usually just paste the whole line if I need to refer to it, but given it a short ID might not be a bad idea.

LoganDark | 7 hours ago

Yeah, the main benefit is being able to refer to specific items rather than ambiguously referring to patterns that might be misinterpreted by the model.

gwerbin | 5 hours ago

Yes, that. And -- in keeping with the theme -- it's just as useful for me, the human, as it is for the model. I can even cross-link them to Jira items, so I can say things like "task EV5 corresponds to Jira subtask DS-7491 within story DS-7389".

Also this is in the context of data science, so I often have a big and ever-growing list of secondary analyses I could run, and each one ends up with a small pile of source code. This actually lets me organize my code around the IDs, so I can have a directory like `analysis/EV7/` with its own little PLAN.md and README and some .sql and .py files and a .ipynb to pull together the results (and/or a small AI-generated data explorer app). And then later if I need to refer to those results I can write a comment like "parameter derived from EV7 results" or whatever.

whizzter | 4 hours ago

git logs are a bit of a pain to search through and also perhaps not the place to insert long instructions, I do remember looking at some repo and just browsing the list made me quickly find what was intended during development.

victorbjorklund | 8 hours ago

Same here. Before I was too lazy on projects where I was solo developer to follow best practice and writing clean code. Now I do it.

deniska | 20 hours ago

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.

nullpoint420 | 2 hours ago

In my experience the agents actually read the AGENTS.md. I used to put info in the README.md but only noticed uptake when I put it in AGENTS.md instead.

Vinnl | 19 hours ago

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.

phailhaus | 18 hours ago

Have you looked at Docker's home page recently? The title is now "Secure Sandboxes for AI Agents". There is some insanity going around, rebranding basic tools as "for agents". Docker is just secure sandboxes for everyone, from that tagline you'd think they were somehow specifically made for agents.

Shorn | 14 hours ago

> Docker is just secure sandboxes for everyone,

Secure? o_O

TheCapeGreek | 6 hours ago

Sure, it can be marketing, but I think it's more that it has become evident that the best way to get agents to write code you can trust, at a scale that actually improves productivity, usually means adopting and enforcing best practices at a scale that the industry silently really wasn't doing at all.

I've spent the last few years banging on a drum about teams installing linters, static analyzers, and similar in Laravel teams. I get nods of agreement from seniors but little willpower from managers, who just want to see the number of commits line go up.

Surprise surprise, now that I am in charge of a project and have enforced these standards, the team has done incredibly well with even just partial AI adoption in their work - because the guard rails are there and agents don't get tired of hitting them.

otherflavors | 21 hours ago

They've gone all in on AI and Agents, how wonderful

prajaybasu | 21 hours ago

Hoping the TanStack Solid 2 adapters are out soon. They're the only blockers for me now.

ryansolid | 19 hours ago

Query, Router, and Start have 2.0 pre-release branches you can install today. Every other library has open PR.

AlexErrant | 20 hours ago

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.

nvme0n1p1 | 20 hours ago

> Did you want to load this TTS player conditionally? Hahah, you can't.

Um, you can? Just change this:

  if (tts) useState(() => loadTTS(tts))
to this:

  useState(() => tts && loadTTS(tts))

AlexErrant | 17 hours ago

I assume you mean `useEffect`.

That does not work because `loadTTS` is actually a hook, so its `useLoadTTS`, and hooks must be top level. I encourage you to look at the pastebin in my link, repeated here https://pastebin.com/sjc3vXTd

So, I must have

    let provider = useGetUserPreference()
    let a = useLoadTTS_A()
    let b = useLoadTTS_B()
    let c = useLoadTTS_C()
    useEffect(() => {
      if (provider=="a") a()
      if (provider=="b") b()
      if (provider=="c") c()
    })
Oh hey, what's that? I have to allocate memory for b and c even though only a is used? THANKS REACT.

hdjrudni | 9 hours ago

Can be simplified a little bit.

  const players = {
    sherpa: SherpaPlayer,
    local: LocalPlayer,
    gemini: GeminiPlayer,
  } satisfies Record<VoiceProvider, React.ComponentType>;
  
  function PlayerSwitcher() {
    const provider = useAppStore.use.voiceProvider();
    const Player = players[provider];
    return <Player />;
  }
  
  function useRegisterPlayer(player: Player, shortPlayer: Player) {
    const { setPlayer, setShortPlayer } = useAppActions();
  
    useEffect(() => {
      setPlayer(player);
      setShortPlayer(shortPlayer);
    }, [player, shortPlayer, setPlayer, setShortPlayer]);
  }
  
  function LocalPlayer() {
    useRegisterPlayer(useLocalPlayer(), useShortLocalPlayer());
    return null;
  }
  
  function GeminiPlayer() {
    useRegisterPlayer(useGeminiPlayer(), useShortGeminiPlayer());
    return null;
  }
  
  function SherpaPlayer() {
    useRegisterPlayer(useSherpaPlayer(), useShortSherpaPlayer());
    return null;
  }

nvme0n1p1 | 2 hours ago

It sounds like `useLoadTTS` shouldn't have been a hook then? You don't have to make everything a hook just because they exist. Hooks are just one tool in the toolbox. There's no shame in a useState or useEffect.

hdjrudni | 9 hours ago

> "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."

That needs to emphasized more. Pretty sure React's Suspense suffers from waterfalls if memory serves.

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.

[OP] pier25 | 20 hours ago

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.

intellix | 15 hours ago

Well yeah, unless it's resumable it's just a matter of personal preference on how you like to organise your overhead of hydration.

baxuz | 20 hours ago

Solid has been my framework of choice for the past 5 years. Haven't touched React since.

techpression | 19 hours ago

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.

miguel-muniz | 18 hours ago

Congrats to Ryan and the team. I never got deep enough into front-end to understand the nuance of these things but I still occasionally tuned into his Friday streams just to listen. You can tell he cares about this subject deeply and I enjoy listening to passionate people talk about their craft.

Tade0 | 6 hours ago

As a frontend developer it's a solid (heh) paradigm shift.

Turns out the secret to fine-grained reactivity all this time was just a tree structure describing the dependencies.

I'm using signals in Angular and while they don't cover every use case cleanly, they're a huge upgrade compared to RxJS Observables - particularly due to how simple and debuggable they are in comparison.

extremeracer | 17 hours ago

Tangential, but since the thread is all DOM: I've been using Solid 2's universal renderer for native watchOS UIs, and just put the renderer and host up as an MIT repo: https://github.com/esensible/solid-watch

The bundle (Solid JSX compiled with the new babel plugin) runs in QuickJS-ng on the watch; the renderer emits node mutations over a small host interface; a Swift host lays them out with Yoga and draws with SwiftUI. The same bundle runs in a browser harness for development. The structure is borrowed from React Native's Fabric: three trees, batched commits, one schema that generates the prop code for both sides. A dozen node types, React Native style names, on purpose.

For context, it's the display layer of a larger personal project (not open source at this point): application state lives in a small expression language with a Rust evaluator, running on the phone or on an ESP32 box, with the state, events and view described by JSON Schemas and a schema-derived wire codec. The watch and an e-ink display are synced views of that state. Bundles and firmware are served and updated over BLE, and the phone app has a sign-in-with-ChatGPT authoring mode that writes the Solid UI and the expression logic against those schemas, checks them on the device, and packs the bundle locally on the phone, no server. Solid's universal renderer is what made the watch part feasible: the UI author writes ordinary JSX and the same bundle runs on the wrist and in a browser tab.

Rough edges in the public piece: you build the QuickJS xcframework yourself, and getting a bundle onto a real watch still means an Xcode build. Examples built with plain npm and the browser harness are in the repo if you want to poke at it. Moving from the RCs to 2.0.0, the only breaking change I hit was <Show> compiling to a ternary, which only reordered mutations inside a commit.

dalmo3 | 15 hours ago

This comment was flagged presumably as AI slop, but it was useful to me to discover that solid now has a universal renderer. For a long time that has been the differentiator in favour of react.

extremeracer | 15 hours ago

... bummer :( I'm real human & been iterating variations of this for a while. Some of my repos deprecated as I discovered solidjs 1 https://github.com/esensible/silkjs https://github.com/esensible/silkflow and an older version of the project I'm working on https://github.com/esensible/extremeracer

troupo | 11 hours ago

Solid has had a universal renderer for a long time, and quite easy to swap out. For example, see https://lightning-js.github.io/solid/#/ (WebGL renderer for Smart TVs)

AFAIK React has never had a properly defined renderer, and it was a pain to swap out

intellix | 15 hours ago

Now we just need Qwik 2.0 to get released for their async resumable framework.

I think with the advent of AI it doesn't matter so much about the DX and your main focus should be on better UX (the best lighthouse metrics) though I don't think their DX is bad either.

FlameWolf | 14 hours ago

A gist I wrote about my experience migrating from Solid 1.0 to Solid 2.0 (RC) a couple of months ago: https://gist.github.com/FlameWolf/7b3be7acb06775f02ea4a57297...

altano | 12 hours ago

If you're sensitive to bundle sizes (which you almost certainly aren't), heads up: the Solid 2 bundles are much bigger.

My counter component bundle test is:

     4.8 KiB (brotli'd) in Solid v1.9.18
    20.3 KiB (brotli'd) in Solid v2.0.0

tommica | 12 hours ago

Oh that is quite the leap

whizzter | 4 hours ago

Meanwhile people using Blazor shipping 50mb of .NET assemblies (maybe it's become better in newer releases but when it appeared that made me nope-out quite quickly).

slowmotarget | 8 hours ago

Oh no! I was about to migrate my JS SDK to v2 and witnessed the same increase:

> The +11.7KB gzip is mostly Solid 2.0’s runtime and the @solidjs/signals scheduler

skrebbel | 12 hours ago

That async cascading dropdown example is very compelling.

simongray | 11 hours ago

Too many things called Solid... I thought this was Tim Berners Lee's project getting an update.

hdjrudni | 9 hours ago

This looks like <Suspense> and Next.js SSR all over again.

I didn't like it then either.

unlog | 8 hours ago

Im so happy about this, got around influencing it, which means a lot, this is the future of all the UI!

dankobgd | 8 hours ago

yawn

mkgiga | 6 hours ago

bought solidjs merch off their store, it's been months of radio silence

varispeed | 4 hours ago

It doesn't explain what is the point of this and why would anybody use this apart from to look cool?

WuxiFingerHold | 3 hours ago

I really like the ideas and concepts (one graph integrating async and reactivity) and also been a fan for some while (watching (at least in parts) Ryans YT streams, having used Solid 1.0 for a smaller project). But I have some mixed feelings knowing that the majority if not all code was written by AI. I have no doubt that every line was reviewed carefully. But this is a very complex code base. And I'm old enough to know that reading is miles away from writing when it comes to understanding. So, I'm sitting here wanting to choose Solid 2.0 for every new project but on the other hand having those nagging doubts whether that project is really sustainable. By the way, those are the same doubts I have for all newly created projects and I usually don't spent a second considering them, but this is a very special case because of Ryan and the team and because of Solid 2.0 being IMO such a significant step in simplifying frontend dev. I guess I need to see a therapist helping me out of my personal AI crisis ... I'm still writing all my code myself and are not left behind like the other dozends of us ;-).

hombre_fatal | 2 hours ago

Ryan Carniato is to Solid as rhickey is to Clojure as evancz is to Elm.

They all convinced me to use their respective languages by sharing all the thought they put into them, especially to address problems in the alternative, more popular options.