DevTools of The Future, JSCONF Asia 2016, Singapore

DevTools of The Future, JSCONF Asia 2016, Singapore

Slides from my "DevTools of The Future" at JSCONF Asia 2016 in Singapore

49f28eff1d0ddf3564a1b8b1f36a6c12?s=128

Kenneth Auchenberg

November 25, 2016
Tweet

Transcript

  1. 3.
  2. 4.
  3. 12.
  4. 14.

    Desktop browsers have changed 2.82% 13.28% 59.39% 10.21% 1.91% (IE

    8.89%) SitePoint October 2016 Source: https://www.sitepoint.com/browser-trends-november-2016-rise-underdog (iPad 5.42%)
  5. 17.
  6. 20.

    Mobile browsers have changed 40.64% 8.64% 5.83% 17.90% 2.65% Others

    1.13% Source: https://www.sitepoint.com/browser-trends-november-2016-rise-underdog 16.69% SitePoint October 2016 6.52%
  7. 26.
  8. 29.
  9. 30.
  10. 43.

    Still a typical debugging workflow Open editor Navigate to page

    Open browser Find file in editor Make change Refresh browser Open DevTool Go to scripts-tab Find same file again Go to the edited line Set breakpoint Debug Switch back to editor Make change Tab back to browser Repeat
  11. 45.

    1. Why do I need to learn a new DevTool

    for each browser? 2. Why do I have to use different tools for authoring and debugging? 3. Why isn't my editor integrated with my browser(s)? 4. Why are DevTools still bundled with our browsers? A few thoughts
  12. 49.

    What if it was like this? Open editor Find file

    in editor Make change Open browser Set breakpoint Debug Repeat Make change
  13. 51.
  14. 59.

    Why is the web one of the few platforms that

    still bundles a full development environment with the runtime?
  15. 66.

    Why are DevTools bundled with our browsers? Desktop browser Non

    desktop devices Chrome-less contexts Devtool
  16. 68.