solid

There are other barriers to adoption besides network effects. I showed in another comment downthread how easy it is to inject React into just the parts of an otherwise static web page that need enhanced interactivity. Svelte and Qwik need to be compiled – if you don't already have a full modern frontend build chain, that's a huge added maintenance cost. Solid, to their credit, does have some support for using it in non-compiled environments: https://github.com/solidjs/solid/tree/main/packages/solid/ht...

Here the creator of Solid compares it to Mikado: https://github.com/solidjs/solid/discussions/485

Looks like its still in the discussion phase, did not see a timeline but also did not read super close. Did learn about the tanstack-router which I had never heard of, so that was worth looking this up right there ;) https://github.com/solidjs/solid/discussions/2425

> SolidJS seems designed right so that it doesn't need so many major revisions and it feels quite stable. lol https://github.com/solidjs/solid/discussions/2425

As always, less complexity and less expressive power at a given level go hand in hand: Deno as it exists right now can’t work even with a relatively tame nonstandard approach to JSX such as that in Solid.js[1] (without essentially running a build step at startup), let alone a full language extension like Svelte[2] (there is a thing for that now[3], but it seems to be squeezing in a build system through a localhost server IIUC?). [1] https://github.com/solidjs/solid/discussions/332 [2] https://github.com/sveltejs/svelte/issues/4431 [3] https://github.com/crewdevio/Snel

I avoid using them, except when having to expose a component to a third party, if they _really_ want the ergonomics of using WCs. Then I'd use something like https://github.com/preactjs/preact-custom-element, https://stenciljs.com/docs/custom-elements or https://github.com/solidjs/solid/tree/main/packages/solid-el.... As far as I see, there is nothing that WCs provide which isn't already solved, in a better way, both for devs and users. And making a framework that use custom elements and shadow DOM for component-based logic and encapsulation seems like a purely philosophical approach to adhere to some vision of "platform purity".

This is where I’m at, too — it’s faster and simpler than React, and less magical than Svelte, but it’s just too immature. As another commenter pointed out, there’s basically one contributor: https://github.com/solidjs/solid/graphs/contributors

This is interesting because it's a bit like Svelte, but it doesn't use the Svelte "language" (which looks like JS and HTML but, in some crucial ways, sometimes isn't). It's a little disheartening to see that it's 3+ years old and has only had a single significant contributor though[1]. It's impossible to avoid single-contributor projects in the JS world, especially with Node, but the alternatives (React, Vue, Angular, and even Svelte) are orders of magnitude more popular, so it's one area that we can play it safe if we need to. 1. https://github.com/solidjs/solid/graphs/contributors

Chechk this benchmark comparing front-end frameworks (includes alpine, react, vuew, svelte, etc) : https://krausest.github.io/js-framework-benchmark/index.html Maybe try https://github.com/solidjs/solid

It will be sad if this UI library makes Tim Berners-Lee's long-term project Solid less visible: "Your data, your choice. Advancing Web standards to empower people." https://solidproject.org/ In the future, people might build UIs for Solid using a (hypothetical) solid-solid or at least combining Solid UI and SolidJS: e.g. https://github.com/solid/solid-ui vs https://github.com/solidjs/solid At least, if SolidJS is supposed [1] to be a name separate from Solid, why not call the repo solidjs like the org? [1] https://news.ycombinator.com/item?id=23375912

Not to be confused with Solid the JS framework (https://github.com/solidjs/solid).