dwyl / dwyl/learn-progressive-web-apps
Server-side Rendering First
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Why is server-side rendering important?
- Clients that **don't support JS** or _chose_ to disable it. see: https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/
- **Bandwidth constraints** where downloading a **2MB `bundle.js`** before showing any content would take 10 seconds or simply time-out!
- **Less capable devices** such as "low-end" phones ([500M](http://blogs.wsj.com/digits/2015/11/01/samsung-sells-more-phones-but-for-less-money/) in use) e-readers ([**100M**](http://www.statista.com/statistics/272740/global-shipments-of-e-book-readers) sold)
Discussion on supporting Non-JS people: http://stackoverflow.com/questions/9478737/browser-statistics-on-javascript-disabled The people who say we should not build for the 1% (or what ever the number for the minority) is are showing a complete lack of empathy for people who might not have the financial means to buy new hardware or are "stuck" in an Organization without out-dated IT.
As far as I can tell, polymer does not support server-side rendering out-of-the-box.
Riot does: http://riotjs.com/guide/#server-side-rendering
Have you been able to find out how to server-side-render with Riot? if so, please share how! (_thanks_!)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.