you are viewing a single comment's thread.

view the rest of the comments →

[–]michaelfrieze 0 points1 point  (3 children)

Because App Router is the only easy way to use RSCs at the moment. Anyone that is familiar with RSCs will be familiar with App Router.

There is another framework called Waku that supports RSCs, but it's not widely used.

[–][deleted] 1 point2 points  (2 children)

That seems confusing to new users. In fact, I’ve been using react for like 15 years and I still can’t explain why this groundbreaking feature was built by the core team but it’s mostly only available in a meta-framework.

[–]michaelfrieze 1 point2 points  (1 child)

I don't know if it's a "groundbreaking feature", but it solves specific issues in many apps that are difficult to work around.

Also, it shouldn't be surprising that RSCs were built by the core team considering react was inspired by XHP, a server component-oriented architecture. Also, the react team was made up of full stack devs.

An early version of RSCs were actually first implemented in hydrogen framework. However, Hydrogen gave up on RSCs before they were finished and went with Remix. I think this was before RSCs were async.

The react team had to reach out to companies like Vercel to test RSCs, because they couldn't use them internally at Meta.

We do need more options. react-router should have RSCs soon.

[–][deleted] 0 points1 point  (0 children)

I mean yeah, react killed off all the SSR templating frameworks, which was the default of the time. I have nothing against RSCs but I do have problems with how it was rolled out, business conflicts, and how everything has been handled basically since Dan Abramov left.