4 ms·
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 loa
by lr4444lr 8y ago
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 thing, IMHO.
- mdellabitta 8y agoIt's good for accessibility...
- Can_Not 8y agoBest practice would be to wrap anything that is both unnecessary for SEO and non-trivial into <no-ssr> tags. No need to render a datetimepicker widget on the server, especially if Google bot is requesting the page.