I was making a point that the best tool for the job can sometimes be the one which is widely used, hugely supported, cheap to host, well understood - it may not be the trendy choice, but "trendy" is not (in my humble opinion) a terribly good criteria for tech stack decisions...
It's not an interesting point, especially if you intend it as a tangential flamewar hook and, as you say yourself, you post it repetitively. The submission is not about 'tech stack decisions', it's somebody showing something they made. You don't have to like it or have much to say about it but a completely generic 'just use something else' is well within the scope of the guideline and a bunch of other ones.
…I’ll just leave this [0] here. A perfect example which just popped up in my feed list of “simple but does this job” tech. No js, no database, a $10 a month vps.
Author mentioned that the reason for the new blog is to be easier to create posts. But doesn't mention much of what changed in the workflow. Seems he's using md files. But then what was he using before? If MD->MD, then what changed? Using Obsidian to be easier to edit and sync between devices?
The author is in the thread so if these are your specific questions or critiques, you should direct them there. 'It's hilarious to me they don't use Wordpress' is not a specific question or critique, it's a generic sneery putdown.
I was making a point that the best tool for the job can sometimes be the one which is widely used, hugely supported, cheap to host, well understood - it may not be the trendy choice, but "trendy" is not (in my humble opinion) a terribly good criteria for tech stack decisions...