Earlier quoted context omitted.
*not having
You don’t have to. Inertia.js exists.
Inertia.js works based on pages as far as I know, right? We need load the data per page. RSC loads per component so I wouldn't call that comparable.
React is winning by default and slowing innovation
861–866 of 866 posts
Re: React is winning by default and slowing innovation
#862Earlier quoted context omitted.
+1 React DX is really great. It started really great and it got weird and bloated but it's still really great relative to the JS landscape hell. But, also yes, it's a pain in the ass and a frustrating kind of necessary evil. So there is room for improvements. Nextjs is a living hell. The ironic thing is AI makes it dramatically more tolerable to the point it's actually pretty good. But that can't be a good thing in t…
React DX is hot garbage. Words cannot express how much I LOATHE hook rules. Coming from a Solid JS background, where reactive primitives are just Javascript functions... I groan every single time I run into (yet another) hook rule. I have to conditionally render empty fragments because React can't handle conditional hooks. It's the stupidest thing ever. "Oh hey let me allocate memory for this hook that will almost ce…
[deleted]
Re: React is winning by default and slowing innovation
#863Earlier quoted context omitted.
This is factully wrong. You are confusing react with nextjs. React produce html documents, and the first usecase was reactdom, a pure client rendering library.
No. I'm speaking from experience having used React from its very first release. You're not only factually wrong about me being wrong, your knowledge is obviously quite limited. React has always initially rendering components on the server, then hydrated on the client. You don't have to take my word for it, download the initial release and try it out yourself: https://github.com/facebook/react/releases/tag/v0.4.0 Go a…
I didn't know that, thanks for the pointer, but ReactJS did start as a client side only framework.
React's history starts around 2010 or so, it was integrated into Facebook in 2011 and Instagram 2012 before being open sourced in 2013. And it was that first open source release that added renderComponentToString: long after React had been deployed on some of the world's largest websites.
Also, renderComponentToString isn't SSR. That term usually implies client side hydration so event handlers work, as React is all about state management. But in that release there is no mention of hydration. You could of course do it by hand by rendering to HTML server side, then replacing the entire DOM with a new client side rendered version yourself if you don't mind wiping user's state in some cases, which of course people do! For SSR to work properly took longer.
And that makes sense. Facebook don't use JS on the server side, at least not in that era, their web servers were all PHP/hack. So what would have done the SSR?
Re: React is winning by default and slowing innovation
#864Earlier quoted context omitted.
No. I'm speaking from experience having used React from its very first release. You're not only factually wrong about me being wrong, your knowledge is obviously quite limited. React has always initially rendering components on the server, then hydrated on the client. You don't have to take my word for it, download the initial release and try it out yourself: https://github.com/facebook/react/releases/tag/v0.4.0 Go a…
I didn't know that, thanks for the pointer, but ReactJS did start as a client side only framework. React's history starts around 2010 or so, it was integrated into Facebook in 2011 and Instagram 2012 before being open sourced in 2013. And it was that first open source release that added renderComponentToString: long after React had been deployed on some of the world's largest websites. Also, renderComponentToString i…
Just as a fun fact, React’s jsx is actually a port of XHP which was initially developed for PHP in 2009 I believe. This would explain why react’s components were class based at first (because php leans heavily towards class based OO programming).
Re: React is winning by default and slowing innovation
#865Please see famous essay,'The rise of "Worse is Better"' by James Gabriel[0] for an appreciation of how long this kind of thing has been happening in software.
[0] https://web.stanford.edu/class/archive/cs/cs240/cs240.1236/o...
Re: React is winning by default and slowing innovation
#866Earlier quoted context omitted.
LLMs favour React and Tailwind because they’re popular , so they’ve seen a lot of them, not because of technical merit. This is the very manifestation of React winning by default and slowing innovation.
Given the quality of some of that combo I’ve seen vomited out, it’s technical dismerit. I wonder if you’re better off with something critical mass enough that an LLM can correctly write it at all but not trained on mountains and mountains of slop.
This has been an interesting realization for me, seeing the LLM well poisoned by its poor understanding of hooks and effects has opened my eyes up to how much the average developer also doesn't understand these things.