SolidJS

“Signals are basically as fast as writing event handlers yourself but way less fragile and verbose.”

“I'd much prefer something like Solid or Nostr where your identity is owned by you and described by a single file.”

“the main problem with something like Solid is, if it takes even an hour to figure out how to get it going”

“starting a project in gleam or within sveltekit/astro/solidjs and then porting it to gleam can be great”

“solid-js 2.0 has a whole "htmx-like" mode that lets you have good interactivity even with js disabled”

“You can fire up a solid project and get close to react's speed and quality”

“solid requires it's own jsx transform, and it's framework (imo) is not as ergonomic”

“could use something like solid and have similar performance but easy tooling integration due to just being typescript and tsx syntax”

“it manages to keep JSX by intentionally swapping to signals and introducing primitives and control flow components to scope the compiler”

“Some other frameworks have in theory no compilation or optimization step while delivering constant performance as the app grows, like SolidJS.”

“IMO those problems are better solved by SOLID pushed by Tim Berners Lee himself.”

“It's capability is impressive, yet I do not like hiding what values are async”

“Async being first class is definitely a paradigm shift compared to other frameworks.”

“Simply put: Solid makes the "dumb and naive code" the optimal code. It takes all the pain of React away.”

“The async features are really interesting, I'll give them a try in my side projects.”

“We've solved declarative async, race conditions/complexity are reduced by the structure of your code.”

“I love Solid as an alternative to react. I've been using it for hobby projects for 5+ years.”

“It's obviously a step forward, but that step could be mean a lot more than it really seems to be.”

“it looks nice on a slide deck and then is a pain to debug”

“Instead, look at Svelte or Solid.js, as they integrate nicely with imperative DOM-oriented JS libraries”

“you can use something that is actually fast on the frontend like solidjs”

“oh I don't plan to npm anything other than something like esbuild and solidjs.”

“it scaled a lot better than it would have in any other framework”

“Fast, small, includes what I need and feels like just writing JS/TS”

“something like solid.js is probably the one that matches how i think of webdev”

“the reactivity model is small enough that you can understand it, and even implement a basic version yourself”

“They should just rewrite that laggy UI in Svelte, Solid, or even vanilla JS. Any of those would work.”

“There are way better libraries to write maintainable code in (svelte, solid, and even vue is better FFS).”

“they also introduce a couple of gotchas and weird syntax”

“Solid beats Gea handily on bundle size, 1:4 uncompressed and 1:2 compressed.”

“Solid signals require you to follow a specific syntax and approach, and has its own gotchas.”

“the dependency tracker can't track _all_ the dependencies”

“dynamic dependency management is not just a nice to have, it's actually critical to why Solid's reactive system is more performant”

“offering a new model for sharing personal data that prioritizes user control, privacy, and transparency”

“The only issue with signals-based libraries like Solid is that they pass signals around instead of values”

“I tried proxy-based approaches before (in Solid) and I _also_ had a lot of problems with async processes.”

“The result is significantly more performant, especially for deeply nested component trees”

“it can be helpful to reach for something like Solid when you get into more complex UI”

“SolidJS and Svelte implement react's developer ergonomics, while having better performance”

“fine-grained reactivity feels lightweight compared to typical React SSR”