11–20 of 74 posts
My two cents: 1) Lack of reliable real time ability to detect device and compute size. 2) Increased computation complexity of what to render - why put that load on the server when devices are now commensurately as fast - or even faster given the trend to distributed services that maximize network throughput over power. I'm not even sure why it was so popular in the first place; client server separation is a good thin…
Universal rendering is widely used in the React ecosystem, in large part thanks to Next.js[0] making it simple to set up and run. Many large sites like Marvel.com, Nike.com, Invisionapp.com, hulu.com and many more run on server-side rendered React, see the Next.js showcase for a more complete list: https://nextjs.org/showcase [0]: https://github.com/zeit/next.js/
[0]: https://leerob.io/blog/things-ive-learned-building-nextjs-ap...
So you have two buckets: web apps that don't care too much about shaving milliseconds from the initial load, and content sites that shouldn't be shipping heavy JavaScript in the first place. The target market for hybrid rendering is the tiny slice of sites in-between those two, so it's a minority of use-cases. Though it is also used by sites in the latter category that are shipping heavy JavaScript anyway and having regrets.
2) What is your motivation? What problem do you think you are solving with server-side rendering?
Of course they are. Lots.
The New York Times. The Intercept. AirBnB. Just off the top of my head.
1) What do you mean by server-side rendering of JavaScript? It sounds like you mean executing JavaScript on the server that otherwise is destined to execute on the client-side. I execute JavaScript on the server/terminal all the time and don't call it server-side rendering . 2) What is your motivation? What problem do you think you are solving with server-side rendering ?
edit: This actually has examples https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
Obligatory plug for Phoenix LiveView: https://github.com/phoenixframework/phoenix_live_view edit: This actually has examples https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
https://vuejs.org/v2/guide/ssr.html
Great for FB/twitter share scraping, google scraping, etc. Also much better startup speeds.
Once you get it configured it's very little additional work to maintain.
I have it set up to do things like determine mobile/desktop depending on the `user-agent` to determine the prerendered page to serve, and then the client side JS takes over depending on the viewport size and will either a) Rebuild (less than 1% of the time) changing the markup from desktop->mobile of mobile->desktop or b) Continue happily