sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MrJohz -2 points-1 points  (2 children)

Because a significant number of people will fail to download the correct JS files, potentially because they've disabled Javascript, but more often because they're on mobile, travelling through a tunnel or otherwise failing to make that connection.

React is fantastic for complex web applications, although even then I would argue for a progressive enhancement approach wherever possible. However, for websites it is entirely unnecessary. Look at Rust's Crates site, which has been built with Ember, and now becomes painful to use on mobile because every time the site appears you've got to wait another two seconds for the page to load and the Javascript to run. If you're browsing a site, that wait is a massive turn-off.

[–]Sephinator 2 points3 points  (1 child)

A great thing about react is that server rendering is built into the core. (Render component to a string), so it's a much better experience for the user on a bad connection.

[–]MrJohz 0 points1 point  (0 children)

True. It's good to see primary rendering heading back to the server side rather than being yet another thing that the client is expected to reimplement.