Published 2026-05-26
An honest update on GPHM
I owe you all an honest update — long overdue. I won't sugarcoat any of it.
Where we are
The last year has been quiet from my end. Patches haven't shipped, bugs haven't been addressed, and communication has been almost non-existent. I see it. I've seen managers leave — including people who've been here for years and who I genuinely respect. That's on me.
The technical reality I should have shared sooner
The legacy site is built on ASP.NET MVC and .NET Framework 4.8 — technology that's now over a decade old and effectively end-of-life. Microsoft moved on years ago, and the tooling around the old stack has become increasingly painful to work with. That's the honest reason the patches dried up: trying to keep that codebase alive isn't a sustainable path. I should have been transparent about this much sooner.
What I've been building
For some time I've been working on a complete rewrite of the website on a modern stack (Astro + Svelte) that runs cleanly on my Mac and works well with Claude Code (AI-assisted development). This matters more than it might sound, because it makes development on GPHM enjoyable again — and a solo hobby project that isn't fun for the developer doesn't get worked on. The new setup is faster, more enjoyable, and built on technology that will still be relevant ten years from now. This isn't a parallel project anymore. It's the path forward for GPHM.
I'm not going to claim I'll suddenly have more hours per week — I won't. What's changing is the leverage per hour.
What's coming
- Target: an open beta of the new site after summer 2026, with the core features in place. It won't match the legacy site feature-for-feature at launch, but it'll be a working version you can actually use.
- The legacy site keeps running through the transition.
- After the beta launches, the work continues — filling in the rest of the features, with the new stack as the foundation.
- Between now and the beta, I'll share progress regularly — screenshots, what's been built, what's next. Not just at launch.
Updates from me will come on the blog and Patreon — that's where to look for what's next.
On the community
To anyone who's stayed through the quiet — thank you. To the admins who've kept things running while I've been heads-down — thank you, especially. If you're frustrated, you've earned the right to be. If you've stayed, you have my real gratitude, and I'll do better at showing it.
More soon. For real this time.
— Anders