Yet Another "Yet Another Blog Implementation" Post

I swear I'm trying to kick the habit, but I have another blog implementation. In fairness, it's been around for a while - maybe since last November or so in some nascent form.

This one came up a lot faster than the last few, given the speed at which software moves now through LLM-assisted workflows. And its existence is defensible for a lot of the same reasons.

I'm pretty sure that Java and Kotlin are going to see more and more attrition in this new world of ours for a few reasons:

1. Even if it is supported, hot reloading isn't ready out-of-the-box or prioritized, and that's a big deal when you want to steer an LLM as it iterates
2. There's a lot of momentum behind other languages, notably Typescript and Python, since it's where a lot of the new vibecoders and entrepreneurially-minded people are ending up
3. Given that developers are running more efficiently than they used to, a lot more of them are going full stack; Java and Kotlin are unfortunately not really catering to that use-case enough to draw a crowd

For a lot of those reasons, I'm moving to Elixir and Phoenix for personal stuff insofar as it's possible and practical. I've also heard good things about Ruby on Rails, but the coin I flipped (ergo God) decided that Elixir was better so we're going with that.

Maybe this one will stick, but then again I always say that.