My Articles

Most discussions don’t touch on the places where CGNAT is an inescapable reality. For many users IPv4 scarcity still feels like a theoretical issue, and they design the internet accordingly.

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.

Something I’ve always loved about writing articles, is that it can start a conversation. Something that I felt was missing however, was the ability to find actual reply articles.

To help combat the effects of AI Search Engines on my blog, I have gone through the process to set up a mailing list. Here are my thoughts on the public offerings currently.

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.

Accelerated Mobile Pages, or AMP, is a web technology championed by Google to improve the browsing experience on mobile devices. Throughout this article, I'll outline a few of the issues that led me to ditch AMP.

NextJS is a framework that I've been using for a few years now. As a framework, I love it. In terms of deployment, though, I've never felt a NextJS site was 'stable'.

This article goes over embedding a Google Web Toolkit (GWT) application on a React website, and a few considerations that must be made when doing so.