Panel Discussion: How Web Developers are Changing Web...
summary
Web developers move from consumers to active spec contributors with concrete wins: the object.assign change that altered exception behavior, the picture/srcset compromise for responsive images, and the long-running Temporal effort now at stage three awaiting stable shipping before polyfills and mass adoption. Advice: avoid mutating built-ins, don’t ship language proposals before stage three, and prefer features implemented in at least two browsers. Tests (Test262, Web Platform Tests) and compatibility tables drive implementations and speed standardization.
AI-written summary · about
chapters (13)
- 0:00Panel introduction
- 2:10Developers in standards early
- 7:25TC39 and JavaScript shift
- 10:13Responsive images and HTML
- 15:34Polyfills and standardization
- 20:54Testing and continuous delivery
- 24:04Versioning and compatibility
- 27:19Speed versus thoroughness
- 29:25Temporal proposal for dates
- 33:18Inspiration from other languages
- 34:41Upcoming JavaScript proposals
- 39:12Performance and security in specs
- 41:42Closing remarks
related talks
34mPanel: Don't Break the Web! - Evolving JS While Keeping Developers Sane
54mHot Topics Panel
28mPanel discussion: State of the Art: Web Platform
30mEnabling Web Developers to Build the Future of the Web
50mProposals in this day & age, taking steps to the next stage
29mFuture of the Web
31mPanel
43mResponsive, Adaptive and Responsible