stevebmark
12 hours ago
I don't think this article is well written, it doesn't really articulate a point other than it's not PHP because
> we've developed solid principles for building UIs
There's not really any substance to this statement or the paragraph it's in. I would skip this article entirely, and I think a much more profound view of this concept is "Mind the Gap" talk by Ryan Florence about dissolving the concept of the network and explicit code needed to manage that: https://www.youtube.com/watch?v=zqhE-CepH2g
I am also miffed that the criticizers of React = PHP are often Rails developers who completely overlook that Rails is PHP on cocaine, it is implicit, untraceable database calls sprinkled across templates, and the more use the worse it gets and it quickly becomes un-optimizable. At least with React API calls are explicit, not magic!
artyom
12 hours ago
Agreed. I was expecting a technical justification on why they're not the same. After all the buzzwords and empty statements, I'm now more than convinced that they are.
terandle
44 minutes ago
I would say react server components are fundamentally different.
PHP starts off powered by the state on server (database etc) and ends there when it hits the client unless you hand it off to a completely different language/system: JavaScript.
It would be really nice if you could instead keep writing PHP-for-the-client which would let you reuse your templates/PHP code/etc but keep all the state on the client so you can instantly do things without round trips to the server.
That's what RSCs are and they are pretty great IMO.
nbittich
11 hours ago
I stopped reading after the first laughing emoji