The third year of the third age of JS

In 2020, Shawn (swyx) Wang wrote:

Every 10 years there is a changing of the guard in JavaScript. I think we have just started a period of accelerated change that could in thge future be regarded as the Third Age of JavaScript.

We’re now in year three of this third age and Swyx joins us to look back at what he missed, look around at what’s happening today, and look forward at what might be coming next.

Discuss on Changelog News

Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!

Sponsors

• Sentry – Working code means happy customers. That’s exactly why teams choose Sentry. From error tracking to performance monitoring, Sentry helps teams see what actually matters, resolve problems quicker, and learn continuously about their applications - from the frontend to the backend. Use the code PARTYTIME and get the team plan free for three months.
• Vercel – Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work. Unlock a better frontend workflow today.
• Sourcegraph – Move fast, even in big codebases. Sourcegraph is universal code search for every developer and team. Easily search across all the code that matters to you and your organization: find example code, explore and read code, debug issues, and more. Head to info.sourcegraph.com/changelog and click the button “Try Sourcegraph now” to get started.

Featuring

• Shawn Wang – Twitter, GitHub, Website
• Jerod Santo – Twitter, GitHub
• Nick Nisi – Twitter, GitHub, Website

Notes and Links

• Reactathon
• swyx’s talk at Reactathon
• The Third Age of JavaScript
• Lydia Hallie’s talk on rendering patterns
• analytics.usa.gov
• The Birth and Death of JavaScript
• The Rise of WebAssembly (Infoworld)
• Ryan Dahl on JavaScript containers
• swyx on The Changelog #467
• The other thing I like about esbuild is that it’s a static Go binary, so I feel more confident that I’ll be able to get it to work in the future than with tool written in Javascript, just because I understand the Javascript ecosystem

Something missing or broken? PRs welcome!

Episode source