Progressive Enhancement is Dead, Long Live Progressive Enhancement

9bf3a766e037b9d5a4da0a6f9d0f4f68?s=47 tomdale
September 25, 2015

Progressive Enhancement is Dead, Long Live Progressive Enhancement

Some say that using a JavaScript framework means sacrificing core web principles—universal access, graceful degradation—in exchange for developer convenience. Are JavaScript peddlers like me the Pied Pipers of doom, leading the community astray from web righteousness? Let’s look at why devs are drawn to the benefits of JS frameworks—and discuss whether the rampant hand-wringing about progressive enhancement is deserved or a relic from an older age.

9bf3a766e037b9d5a4da0a6f9d0f4f68?s=128

tomdale

September 25, 2015
Tweet

Transcript

  1. 2.
  2. 3.
  3. 5.
  4. 7.
  5. 8.

    Pages that are empty without JS: dead to history (archive-

    org), unreliable for search results (despite any search engine claims of JS support, check it yourself), and thus ignorable. No need to waste time reading or responding. Because in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web. All your fancy front-end-JS-required frameworks are dead to history, a mere evolutionary blip in web app development practices. Perhaps they provided interesting ephemeral prototypes, nothing more.
  6. 9.
  7. 11.
  8. 12.
  9. 13.
  10. 14.
  11. 16.

    • Works offline • No page reloads (great for e.g.

    music players) • Fast • Rich interaction • Access to device features (camera, storage, GPS)
  12. 17.

    Over the next few years almost all of the people

    who don't yet have a phone will get one, and almost all of the phones on earth will become smartphones. A decade ago some of that was subject to debate - today it isn't. What all those people pay for data, and how they charge their phones, may be a challenge, but the smartphone itself is close to a universal product for humanity - the first the tech industry has ever had.
  13. 21.

    When you have a supercomputer in your pocket, but intermittent

    connectivity, the ability to work OFFLINE is the key to ubiquity
  14. 22.
  15. 24.

    HTML + HTTP + maybe JS client-side JavaScript progressive enhancement

    JavaScript slow devices, good network fast devices, bad network technology best for
  16. 25.
  17. 26.
  18. 28.

    AND the age of the slow, incapable device is coming

    to an end BUT connectivity remains imperfect, even in developed countries IF progressive enhancement is about preserving the ubiquity of the web
  19. 30.
  20. 31.
  21. 32.

    Progressive Enhancement • Works if JavaScript fails to load •

    Easier to archive and index • Faster initial load times
  22. 36.
  23. 37.
  24. 39.
  25. 40.
  26. 44.

    • Smartphones are eating the world • Connectivity is the

    weak link, even in developed countries • JavaScript frameworks are taking over, for good reasons