solid-docs VS solid

Note: Astro supports a variety of popular frameworks including React, Preact, Svelte, Vue, SolidJS, AlpineJS and Lit with official integrations. While for other frameworks e.g. Angular and Qwik, you may still benefit from this tutorial and you would need to further set up the community maintained framework integrations.

The most common and well known is React, with many others sharing this space, such as Svelte, SolidJS, Angular, Vue, Qwik and more. All are impressive feats of engineering and come with bold statements.

GitHub | npm | website

As always, for more information and resources, you can check out the official documentation for SolidJS. We hope this blog gave you insights to easily make the SolidJS vs React choice!

The DSS UI library serves as the central pillar of DSS Template, built with react-aria to ensure accessibility-first, headless UI components. While React is the selected framework for the template, DSS is meant to be easily adapted to other frameworks like Vue or Solid. This adaptability allows teams to choose the technologies that best align with their project needs without being locked into a specific stack

For our frontend, we’ll make use of Solid.js. Let’s introduce Solid.js a bit before moving forward.

- SolidJS (fine-grain, fastest, most consistent) (dx similar to react) (small ecosystem)

[1] https://www.solidjs.com/

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

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

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

Tip Learn why JavaScript frameworks need keys to render arrays. Also learn why SolidJS is an exception to that

You can read more about it and leave your thoughts here: github.com/solidjs/solid/discussions/2294

GitHub | npm | website

The reactivity core, which is in https://github.com/solidjs/solid This is where you'll see the reactivity runtime implementation. Take note that Solid's reactivity doesn't rely on compile-time magic

I did try this but I'm not sure what you mean with the ssrLoadFrom. Is there any documentation on this, all I could find was the examples folder in solidjs: solid-ssr?

This is very true. I really hate svelte single file components. But then I tried JSX for breaking things down. I love solid but I don't feel really good about angle brackets within C style syntax. I saw this Scala library that stick with simple statically typed function syntax than html tags. I don't understand why people still wants to stick with xml like tags. In laminar markup is written like this scala div( h1("Hello world", color := "red"), inputCaption, input(inputMods, name := "fullName"), div( ">>", button("Submit"), "<<" ) ) I wish solid team makes their HyperScript syntax as performant as JSX.

What is Solid?