My Articles

Most JavaScript tooling is being rewritten in non-JS languages. Is this a sign that JavaScript is bad, or is it a sign that we’re finally taking it seriously and forcing it to mature?

Last year I wrote an article about what I was going to keep an eye on in 2025 in the JS ecosystem. It was fun and introspective to write, so here’s the 2026 edition.

JavaScript as a language is heavily asynchronous, with promises being deeply integrated. While this is sometimes the best solution, can the overhead of promises pose a problem for hot code?

2024 has been an interesting year for JavaScript. These are the projects I'll be watching, as well as the projects that I'm leaving behind.

My site has used Gatsby since 2019, but that framework is abandoned. I've moved to Vike, a framework built on top of Vite, and I'm loving it.

Knip is a great tool for identifying and cleaning up unused code, and you can make it even more powerful using their preprocessor feature.

Web bundlers such as Webpack are a great tool to deploy web apps, but for more complex programs, bundle size can quickly become an issue.

JavaScript may not seem to be the ideal language to manipulate large amounts of data. This post goes over a few key problem areas and how you can avoid them.