Here's an objective comparison that Ryan Florence (Remix co-creator) made showing a Remix Hacker News Clone (not the one posted, but one he built himself) vs the Next.js implementation you're talking about here: https://remix.run/blog/react-server-components

If React Server Components can improve things for Remix (they can't right now, but maybe they will get better?) and if it is ever released (it's been 5 years now... and they still are saying they've got a long way to go), then Remix will ship support for them and it will be a non-breaking change for Remix users.

Hey Kent, could you please disclose that you work for Remix as well?

I was coming to say something like this, also if Remix ever supports RSC it will most likely (IMO) be under noticed, like you just name a route `.server.tsx` and it will be a RSC and that's it, I don't think Remix will need a breaking change for this and RSC seems more like an implementation detail Remix has rather than something super big for the framework.

What's been 5 years? Server components were first shown off just over a year ago. If you mean suspense as a whole, then sure, it's been in the kitchen a long time.

Maybe so anon3433...

I totally love code sponsor ️

Thank you, Kent! Your OSS efforts deserve to be funded!

Thanks for sharing glennreyes

You'll be interested to know that Dan Abramov is on the JavaScript Air panel. This is relevant because of this: https://news.ycombinator.com/item?id=10909199 :-)

Agreed. That's why I invited him on the JavaScript Air show. The live video broadcast podcast all about JavaScript and the web platform. He'll be on live on March 2nd: http://jsair.io/lodash

I updated the post with a link :-) thanks for the feedback!

Thanks for the feedback. I've updated the post

I'd say that it's likely that Jasmine's more common, but both are quite popular. I personally prefer Mocha/Chai syntax.

There are definitely more lessons to come!