Blitz VS Svelte

Blitz is also an open-source project that allows users to access the code and allows to contribute. Their community has generated a lot of impact as well, and has grown rapidly over time since the creation in 2020:

Not yet, I actually just whipped it up quickly last week after I was browsing the Notion subreddit and it reminded me of myspace.

These are the tools I used:

* BlitzJS (https://github.com/blitz-js/blitz)

Maybe you could help/join this project? https://github.com/blitz-js/blitz

Hello, I'm the creator of Blitz.js (first announced 2.5 years ago)

Today the Blitz.js 2.0 pivot to a modular Next.js toolkit reached Beta status [1]

Previously Blitz abstracted Next.js, but Blitz 2.0 is now a modular toolkit that plugs into any new or existing Next.js app. Blitz picks up where Next.js leaves off, providing libraries and conventions for shipping and scaling small to large apps.

When I first created Blitz, my aim was to have an all-in-one fullstack framework for Javascript like Ruby on Rails. But that proved to be too difficult. I've decided that achieving an all-in-one framework for JS like Rails is too difficult unless you have a ton of funding and don't have to make meaningful money.

The difference with JS is that client-side frameworks like React have an incredible amount of complexity. Trying to manage all of that and all the other fullstack framework stuff like API layers, auth, file uploads, etc is too large of scope.

So now Blitz is no longer trying to do it all and is focusing on all the non-frontend functionality you need to ship web apps.

Going forward, we want to be the most trusted technical resource for rapidly building and scaling full-stack TypeScript apps.

[1] https://github.com/blitz-js/blitz/releases/tag/v2.0.0-beta.1

Svelte and specifically, SvelteKit is an open source web framework that makes developing web applications easier.

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

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…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.