Why Is Everyone So Mad?

preview_player
Показать описание
I keep seeing people worrying about React Server Components, and I wanted to talk about it

S/O Ph4seOne for the awesome edit 🙏
Рекомендации по теме
Комментарии
Автор

If one likes RSC, one must read grug developer. One must stop be big brain and to love complexity spirit demon

yegorzakharov
Автор

I have seen u mention million times that app router has made u more effient.... actually can u show that to us by writing some code what efficiency boost are u actually getting cause we viewers aren't feeling that way

copilotcoder
Автор

If something I've learnt in life so far, is that if someone constantly making excuses, and saying something is NOT happening, usually it means that in reality everything is other way around

Like_a_lion_
Автор

Not convinced that somehow using Server components makes things more simple. With Next you gotta use a magic "fetch" function that magically caches things on the root level of a component where it was called. You now gotta move some of the components that need client-sided logic to some other components with "use client", and you'll probably do it at least 40-50% in a production app.
You'll move all heavy lifting to the server, which you have to pay for now. Before it was client-sided and it depended on customer's device, and current smartphones are quite fast, so as someone who's been using React for +5 years, I do not support this change.

aleksd
Автор

SolidJS has been simpler since I switched.
• Good docs ✓
• Signals for reactive updates ✓
• Clean separation between visuals of component from the data in that component ✓
• Built in support for data fetching like Tanstack Query - extremely useful✓
• createEffect is much simpler than useEffect ✓
• Good support for standard HTML DOM ✓
• Not requiring special package to make standard JS packages work ✓
• Event handlers support full javascript ✓
• No hook rules ✓
• No keys in maps, use a For which does it for you ✓
• Switch statements for mutually exclusive logic ✓
• Big project moved over in less than a sprint, code got simpler and more maintainable at the same time ✓

joshring
Автор

I feel like either Vercel needs to come out and say Nextjs 13 is NOT production ready, or this new model isn't the right way to go, because I often find myself fighting with RSCs rather than just building what I want. It is just so limiting it's driving me crazy. For example there's currently no non-hacky way to retrieve query parameters in a RSC that's not a route page component. Imagine you are building an ecommerce site page in which you list items based on the pagination data you read from url. You can't fetch items in a deeply nested list RSC because it can't access query params. Best you can do is retrieve them from route page component and prop drill them...

But the bundle size is reduced by 2kbs so congrats I guess.

TightyWhities
Автор

Learned alot reading the comments on this video

jonesaa
Автор

the closer u get to next js folks the less i trust..and i like vercel they are great but i dont see how its an objective take. everyone else can't be that ignorant

dixztube
Автор

Show 👏 us 👏 code 👏! Give us examples rather than just saying stuff.

Twas-RightHere
Автор

I would love to see a video of you going over examples of when you would personally use react server components.

zachariahtatman
Автор

if I'm being honest, I'm getting sick of react and really considering picking up another framework. the reason that made me choose react are the same reasons that make me hate it. add to it all those changes, and I'm really sick of it.

chawkichalladia
Автор

Summary: it's time to move to Svelte 😂

karolus__
Автор

The server-focused conceptual shift in react will not work because it is not a simple shift in developer skills, it is a shift in the higher level of development, in the distribution of work structures, which is not possible for most companies,It is also full of confusion for beginners and definitely has a negative impact on the future of react

butterfly
Автор

How does this make fetching data from server easier? For most applications it has been trivial for at least 10-20 years already... Yet another JS solution to a nonexistent problem :)

eero
Автор

I feel React (in general) has forgotten that most React developers don't actually use React (or even JS) on the back-end. Sure, have your cool server-side features if you want but please don't break the experience for the rest of us.
We've all seen this kind of thing happen before. And it looks like it's happening again.

Don't alienate your base. We might not be loud. We might not be exciting. But we are the reason you are here.

I'm not quite ready to jump-ship. But I DO have contingencies ready...

MojoMagicau
Автор

After 20+ hooks you have to learn, rendering optimisation, the verbosity, etc.now you have a new toy in town. Yeah, don't count me in. I had some of my worst experience with react and it's getting worse.

oumardicko
Автор

I’ll just stay sitting at the top of my Vue tower looking down on all the unhappy front end react devs 😅

MickDavies
Автор

HTMX and SolidJS SPA both seem to have a better model for 85% of use cases.

kigyak
Автор

Svelte is the always fucks my tried Svelte recently and man!!! it so fucking easy and

zainbaloch
Автор

IF Vercel implement the worst thing ever, this guy will still make a 20min video how the idea is great.

mdtron