I broadly agree with those who are saying there’s no real business case these days for users with JavaScript explicitly disabled. I’d also disagree with those who are saying you need server rendering for search engines; Google and others now support JavaScript.
However, for me the real strength with the server rendering is getting a readable/usable page to the user faster, particularly when that user is on a slow connection and/or an underpowered device , the combination of which might mean it would take 10+ seconds to download and execute the JavaScript and render the first view.
Going a step further, one could imagine doing a bit of client-side logic based on the aforementioned conditions to decide whether to load the JavaScript app at all or just let the server rendering handle it.
I’m interested to see where this goes with React, Angular and Ember over the next months and years. Great article, Jack.
David Goss
I broadly agree with those who are saying there’s no real business case these days for users with JavaScript explicitly disabled. I’d also disagree with those who are saying you need server rendering for search engines; Google and others now support JavaScript.
However, for me the real strength with the server rendering is getting a readable/usable page to the user faster, particularly when that user is on a slow connection and/or an underpowered device , the combination of which might mean it would take 10+ seconds to download and execute the JavaScript and render the first view.
Going a step further, one could imagine doing a bit of client-side logic based on the aforementioned conditions to decide whether to load the JavaScript app at all or just let the server rendering handle it.
I’m interested to see where this goes with React, Angular and Ember over the next months and years. Great article, Jack.