solid-docs VS Svelte

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…

The core mapping engine is MapLibre GL JS, a powerful open-source web map library 3. The front-end web framework of choice is Svelte, which MIERUNE has adopted company-wide as its default stack.

Personally, I (@trueadm) have been involved in some truly amazing frontend frameworks along their journeys — from Inferno, where it all began, to React and the journey of React Hooks, to creating Lexical, to Svelte 5 and its new compiler and signal-based reactivity runtime. Along that journey, I collected ideas, and intriguing thoughts that may or may not pay off. Given my time between roles, I decided it was the best opportunity to try them out, and for open source to see what I was cooking.

I went with SvelteKit to make everything easier for me (feel free to use what works for you to achieve your goal). I also used TailwindCSS' preflight script to reset the default browser styles to make styling super easy.

I come from js/ts as well I find snake case much more readable now. There are even js/ts projects that use snake case despite the convention for readability

https://github.com/sveltejs/svelte/issues/3479#issuecomment-...

I primarily work on Windows, though I also use Linux, so I needed a cross-platform solution. I chose Electron for its flexibility and paired it with Svelte, TailwindCSS, and Vite-Electron. Vite made dev setup fast and clean, which I really appreciated.

a svelte5 spa

Svelte continues to earn a reputation as the joy-to-work-with framework due to its lightweight nature, elegant syntax, and compile-time reactivity. It is often used for side projects, hobby apps, and small websites, but Svelte isn’t just for passion projects.

tools: sveltekit, pocketbase, postmark, groq, docker, cloudflare, cloudflared.

The first time I visited https://svelte.dev , the non-flat-vector banner instantly won me. It just stands out from the world around it. I just sort of assumed the engineering was superior to the competition if they were going to lead with crimped metal (and was right).

Flat design has always struck me as an extremist response to an issue. Windows Vista required everyone to be on the same page design-language wise in order to look good, but can the same be said of Windows XP? You can make just a few parts of your app drop-shadowed, you can add some slight reflection gradients while keeping the whole thing matte, you do not need to get rid of all visual depth just to avoid the feeling of zeerust.