3 ms·
@danabramov, would love to hear your stance on that
by halflife 2y ago
@danabramov, would love to hear your stance on that
- danabramov 2y agoI didn't really attempt to motivate it from the practical standpoint in the article. The article aims to be more of "reinvent some old ideas from first principles, while explaining some novel parts" kind of thing. In particular, the callback to Miguel's article about async/await (https://tirania.org/blog/archive/2013/Aug-15.html https://tirania.org/blog/archive/2013/Aug-15.html) is intentional. I'd like to see some parts of my article as making a similar argument for 'use client' / 'use server' and the concept of first-class cross-environment references module system. And as for practical benefits, I think the main benefit is composition--ability to compose and weave Server/Client building blocks together. Of course there's been myriads of approaches to server/client apps but I've never seen anything with the same compositional properties as RSC. I think Sam's talk (https://www.youtube.com/watch?app=desktop&v=9CN9RCzznZc https://www.youtube.com/watch?app=desktop&v=9CN9RCzznZc) makes an amazing argument in favor of that viewpoint so I'll defer to him.
- halflife 2y agoThanks for the explanation, I understand that wasn’t the point of the article, I’m one step before trying to understand the motivation behind server components :) Obviously the technology is impressive, basically serializing code over the network. I’ll look into Sam’s talk.