[gumboza]

Server side rendering with light weight JavaScript. The point you make about most cases not needing it is spot on.

[Gigachad]

This is how most products start and then inevitably it starts to require more complex interactive pages so you have to add react and then it becomes easier for everything to be react.

Client side rendering is not strictly tied to single page apps. At a previous company we had rails render out a div containing all the data the page needed to mount the react component. No complex api design, no weird permission issues, etc.

[gumboza]

I’ve worked on extremely complex projects (many hundreds of endpoints, many TB of data). React definitely does not scale for those at all. It has a niche for a few use cases but it’s terrible for most I have found.

It’s all about applying the correct solution to the problem and that isn’t the web if it involves react.

[ojr]

React scales for Facebook level traffic, I doubt there are many use cases where projects need to scale React to serve more users than Facebook

[gumboza]

Facebook does a few very simple things lots of times a second.

It doesn’t scale to lots of different things regularly.

[dmak]

I've done that before, and it works well especially if that data doesn't frequently change or grow too big.

[egeozcan]

This sounds more like a wish than a prediction. I'm saying this as someone who used to love intercooler.js (and really dislikes htmx).

[gumboza]

It’s a necessity. The end user experience for React isn’t necessarily the best.

Where it exists, the web is probably the wrong solution for the problem.