Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Progressive Enhancement is Dead, Long Live Progressive Enhancement

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.


September 25, 2015

More Decks by tomdale

Other Decks in Programming


  1. Progressive Enhancement is Dead LONG LIVE PROGRESSIVE ENHANCEMENT

  2. None
  3. None
  4. progressive enhancement (n.) rendering HTML on the server, then adding

    behavior using JavaScript
  5. None
  6. Only you can prevent JAVASCRIPT SHAMING

  7. None
  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.
  9. None
  10. THE WEB for granted don't take

  11. None
  12. None
  13. None
  14. None
  15. Using JavaScript has REAL BENEFITS

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

    music players) • Fast • Rich interaction • Access to device features (camera, storage, GPS)
  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.
  18. A Tale of Two Supercomputers 50ms

  19. A Tale of Two Supercomputers

  20. SMARTPHONES will be more pervasive than CONNECTIVITY

  21. When you have a supercomputer in your pocket, but intermittent

    connectivity, the ability to work OFFLINE is the key to ubiquity
  22. None
  23. HTML HTTP User Agent HTTP HTTP!

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

    JavaScript slow devices, good network fast devices, bad network technology best for
  25. None
  26. None
  27. In other words

  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
  29. We should all be building offline apps with… JavaScript!

  30. None
  31. BUT!

  32. Progressive Enhancement • Works if JavaScript fails to load •

    Easier to archive and index • Faster initial load times


  35. The best way to make someone do something is to

    make it free
  36. None
  37. None
  38. FastBoot Progressive Enhancement for Ember.js

  39. None
  40. None
  41. Progressive Enhancement JavaScript Frameworks vs.

  42. I agree: The web is about UBIQUITY

  43. Sometimes we need to RETHINK our assumptions

  44. • Smartphones are eating the world • Connectivity is the

    weak link, even in developed countries • JavaScript frameworks are taking over, for good reasons
  45. Let’s take advantage of these trends while preserving the ubiquity

    of the web
  46. Not try to shame people back to an outdated model

  47. THANK YOU tomdale