React VS Svelte

[1] ForesightJS Official Documentation: https://foresightjs.com/docs/intro/ [2] React.js Official Documentation: https://react.dev/ [3] Web Performance Optimization:https://web.dev/explore/fast

From what I understand of the RSC protocol which the post is based on (might be wrong since I haven't looked closely at this part), this is supported: https://github.com/facebook/react/pull/28847.

>The format is a leading row that indicates which type of stream it is. Then a new row with the same ID is emitted for every chunk. Followed by either an error or close row.

This article assumes the reader is a developer that knows their way around Markdown, TypeScript, React.js, and [Next.js] https://nextjs.org/). Familiarity with Tailwind-css would also be useful.

In mid-2000s Gmail revolutionized web development by becoming the first true SPA project. Its seamless user experience inspired developers worldwide to adopt this new model, leading to the creation of frameworks like React, Angular and Vue.js. SPAs became the go-to solution for many applications, which required real-time interactions and a fluid user experience.

React because it’s a widely popular front end library

Vite Documentation Next.js Documentation React Docs

Source: React.js Github

🔵 React

Metadata is huge - One may expect package metadata to be smaller than package contents. The results show, that exactly the opposite is true with package content size being about 53 MB, while package metadata size being about 77 MB (or 81 MB for Nexus). This should be no surprise since metadata contains all package versions, which can easily be more than a thousand as evidenced above for the react package.

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.

Svelte as the main framework. (Whimsy is my first Svelte project, actually! And Svelte didn't disappoint. Almost.)

We're going to build our Svelte application using the Svelte REPL sandbox (or just REPL) at svelte.dev. I recommend checking out all the great documentation at svelte.dev, like its Examples section showcasing Svelte's many features, as well as the cool interactive tutorial at learn.svelte.dev.

Svelte super clean frontend structure

In theory, “de-frameworking yourself” is cool, but in practice, it’ll just lead to you building what effectively is your own ad hoc less battle-tested, probably less secure, and likely less performant de facto framework.

I’m not convinced it’s worth it.

If you want something à la KISS[0][0], just use Svelte/SvelteKit[1][1].

Nowadays, the primary exception I see to my point here is if your goal is to better understand what’s going on under the hood of many libraries and frameworks.

[0]: https://en.wikipedia.org/wiki/KISS_principle

[1]: https://svelte.dev

When I teased this series on LinkedIn, one comment quipped that Vue’s been around since 2014—“you should’ve learned it by now!”—and they’re not wrong. The JS ecosystem churns out UI libraries like Svelte, Solid, RxJS, and more, each pushing reactivity forward. React’s ubiquity made it my go-to for stability and career momentum. Now I’m ready to revisit new patterns and sharpen my tool-belt.

What is the advantage over Svelte (https://svelte.dev/)? Especially since Svelte is already established and has an ecosystem.

At Project Au Lait, we are developing and publishing an open-source asset called SVQK, which combines Svelte (Frontend) and Quarkus (Backend) for web application development. The asset includes automated testing tools and source code generation tools. This article introduces an overview of SVQK. (For instructions on how to use SVQK, refer to the Quick Start.)