For a long time I wanted to create a blog, mostly to rant about capitalism, but also to provide technical insights about software engineering. However, whenever I tried, I always struggled with the following things:

• Which technology to use?
• How to structure posts?
• Should I wire tree-sitter in order to highlight code blocks?
• And other even scarier existential questions...

Then I realized my HTML and CSS skills were no longer what they used to be, specially after tools like React and Tailwind CSS became a thing. That was a sign that maybe I should avoid too many abstractions and go back to the basics.

Also, being paralyzed due to the many choices available prevented me from achieving the main goal: being able to blog and spread my thoughts publicly. If I didn't accomplish that, there was no point in investing that much time and putting so much effort into a blogging framework anyway. I can—and most likely should—invest my software engineering skills into other more interesting projects, like my own window manager, for example.

In conclusion, the most important thing of a blog is its content, not its technology. The chance of good ideas to last longer than fancy technology is way higher than the other way around. So here I am. No frameworks, no static asset generation, only handwritten HTML/CSS/JS files.