The State of JavaScript – The State of the Web




Rick speaks with Addy Osmani about the state of JavaScript. Addy is an Engineering Manager on the Google Chrome team, and he has been a web developer for 17 years. He has a deep understanding of JavaScript, as it is today and how it’s changed over the years, and he shares his insights in this episode of The State of the Web.

Resources for measuring the state of JavaScript:
Lighthouse → http://bit.ly/2yJjqkb
WebPageTest → http://bit.ly/2Cm911h
HTTP Archive → http://bit.ly/2Cl3tUA

Resources for using JavaScript responsibly:
Code splitting → http://bit.ly/2Ez97Wa
Tree shaking → http://bit.ly/2AdQNgP
Webpack bundle analyzer → http://bit.ly/2QUTnxJ
Source map explorer → http://bit.ly/2CMroNJ
Managing third party JavaScript → http://bit.ly/2P0ecuC
Lazy loading → http://bit.ly/2yhfN5B
Feature Policy → http://bit.ly/2PE5Kye

Resources for monitoring JavaScript performance:
Performance budgets → http://bit.ly/2yhfyY8
Lighthouse CI → http://bit.ly/2pV81tt
SpeedCurve → http://bit.ly/2pYKCap
Calibre → http://bit.ly/2NMoud0

Watch more State of the Web episodes here → http://bit.ly/2JhAzsh
Subscribe to the Chrome Developers channel to catch a new episode of The State of the Web every other Wednesday → http://bit.ly/ChromeDevs1

Original source


24 responses to “The State of JavaScript – The State of the Web”

  1. A lot of this is due to business requirements, I.E. the trend to have the frontend completely separate from the backend so that the backend is just API, so that the same API can be deployed cross platform. That led to the rise of things like React, which require twice as much code to do the same thing just because people went "Oh cool look how fast it renders! We must build everything in React now!", and enforces all these insane rules about one way data binding for the sake of the all mighty "convention". Then usually about 30-40 libraries on top of that to get you out of the hole that React creates. The issue is not momentJS lol. But what can you do? Most businesses are way to strapped for cash and time to be worried about optimizing to that level. If you're worried about minimizing your JS code base because it's over 1mb, it's either because there is some sort of technical limitation you're hitting due to it, or you're somehow completely out of other much more critical issues, which has never happened anywhere I've worked in 15 years.

  2. ad networks and other 3rd party scripts that deal with user data are BY FAR the biggest problem with web performance and destroy the user experience. I wish this topic was discussed more in public mediums such as twitter, etc. Chrome has been THE leader in advancing browser features and security and I hope they consider '3rd party scripts' as an important problem.

  3. I think the Turkish government had the Saudi Consulate bugged, the iWatch theory is just an excuse. They must have some gruesome video (not just audio) evidence about Mr. Khashoggi's body being hacked to pieces, his skull and genital removed by the Saudi's autopsy surgeon with his bone saw.

  4. One thing I really dislike about these types of things, and other content google puts out recently, is stuff like "promises are well supported for a few years now"; yeah, if you're talking about evergreen. Almost all actual web-developers still need to support IE11. I mean sure, it'd be better to only include those polyfills on IE11, but this whole pretense that IE11 doesn't exist or doesn't still typically need to be supported is absurd.

Leave a Reply