solid-docs VS solid-start

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…

I have not tested anything on SolidStart, TanStack Start, or React Router. I am personally not a React fan, but it is probably easier to get them to work than other frameworks. SolidStart uses Nitro, so it should be similar. Qwik 2 will probably use Nitro when it is released as well.

The unjs project is an example of our commitment to go further, together, and I'm delighted to see other frameworks are joining us in building on top of Nitro.

SolidStart. Fine-grained reactivity goes fullstack.

As much as this is exciting news, it does mean that sadly I'm moving on from Netlify. Netlify which has been my home for the last 2 years and who believed in us(and me) before anyone else did. Their support is what made SolidStart possible. I've learned so much about deployment and infrastructure working closely with the Frameworks and Primitives team. I've traveled the world giving talks alongside the Developer Experience team. In this role, I've had the opportunity to work with some of the most amazing people inside and outside of Netlify.

Only, if you're going to write a fullstack app and have server rendered or statically rendered pages, you'll most likely use a meta framework like NextJs, Remix, SvelteKit, SolidStart.

You can read more about it here: github.com/solidjs/solid-start/releases/tag/v0.7.0

Solid-start is the long awaited meta-framework for Solid.js. Since it entered its second beta after a rewrite, there were a few breaking changes, so the previous article on this one's topic was no longer valid.

Solid Start a metaframework (think Next/SvelteKit/Remix) is still a work in progress: https://github.com/solidjs/solid-start