[rglover]

> Server Components are guaranteed to become the standard for developers who need SSR

I sincerely hope not. This is a serious detour from how web apps inherently work. Not good because it means people who start with React—likely a large number of devs—are not going to understand how the web works (and will potentially create destructive messes themselves later).

I was able to solve this problem in my own framework with way less hoop jumping: https://github.com/cheatcode/joystick.

What you describe seems like a ton of overhead for what is effectively sending some data-populated HTML, CSS, and JavaScript back to a request. Perhaps I'm misunderstanding something (or it's just an idiosyncrasy of React).

[sergiomattei]

> Not good because it means people who start with React—likely a large number of devs—are not going to understand how the web works (and will potentially create destructive messes themselves later).

You could say that about any abstraction. Frameworks, cars, etc. It couldn't be furthest from the truth.

[rglover]

You can design abstractions in a way that doesn't remove the fundamental concept from the workflow. So, no, sorry.

I used to buy this line of thinking but having done the work myself, it's clear there's a serious lack of thinking before doing. Having worked with React since the early days (~2015) and watching its evolution, these ideas stick sheerly out of popularity, not coherence or clarity (read: the changes over the years have been degenerative, not additive—the original React was clear).