When nullvuild was developed, the first language chosen was Python Django.
At the time, I was thinking about a half-mix of blogging platforms and web apps, not just web apps, so I deliberately chose Python because the documentation was well done, the ecosystem was broad, and above all, it looked scalable.
But the patch came from an unexpected place.There were few places to host Python cheaper than I thought.Now things might be different, but then the choice was really limited.
Eventually, the service was run on PythonAnywhere, which was too slow, damaging the user experience, and a problem that could no longer be delayed, so I later switched to PHP.
At this time, there was no AI that directly controlled my system like Claude Codex or Codex now. Yet a web-based LLM was enough to switch languages and adapt to the new stack.
One of the greatest lessons I’ve learned from this experience is that because everyone else writes it, I don’t have to insist on the language or the environment.
After all, there are only two things that matter: how cheaply it can operate, and how well it fits my situation, because the rest of the functional parts will be filled by AI anyway.
It is a time when the criteria for technical choice move from ‘tradition’ to ‘compatibility’, and one of the first people who felt that change was probably me.
Loading comments.