Comparing SvelteKit to React Server Components

[DEVDerr]

Once again, React does not try to give an opinion about some aspect, which might be cool to experiment with or, but should not be really used in the company if you have developers with different opinions.
It's cool for personal usage (or for same-minded people) to be able to define such a boundary by yourself, but in serious application that is maintained and developed by multiple developers, such boundary has to be defined by a framework. It's opinionated and that's very good
And personally I like the way SvelteKit does it. I fetch and process the data on the backend which gives me clean data to present on the frontend. And the cool thing is that I don't need some kind of tRPC or other libraries to infer on the frontend what backend returns me.

Ofc since it's a codegen, in my NeoVim I have to run `:LSPRestart` from time to time, but still I would pick this pre-defined by a framework boundary any day, over what RSC-land offers

[yarmgl]

I kinda like the sveltekit model, but using something like nuxt which allows mixing server and client code in the same component is amazing as well

[Kane]

The thumbnail is not offending enough people. I could barely see you…

[raph]

what you want is a svelte component that is marked to only run on the server right? It's true that the current model implies that you make the choice at the page level, not the component level. You can still make this happen using pages right? some server and client pages and layouts to assemble them?

[ISKLEMMI]

This channel is looking real nerdy already. Instasubbed!

[NiklasZiermann]

Really excited to see a channel with less effort for reach and more focus on good info :)

[QQ-xxmo]

React is becoming more svelte than svelte itself, how cool ?