This was a great read. Thanks to the author for the vulnerability.
In this thread and others, HN does a lot of talking about the fixed properties of these languages and frameworks.
Something I don’t see much is: choose the tool that you and your team are most familiar with.
It’s relatively easy to learn a new language, but it takes a long time to learn an ecosystem. Learning that ecosystem takes time away from focusing on your customer.
I recently started a new web app and tried to use Django because of the batteries-included framework “should” have been the right tool for the job.
But I haven’t used Django in 15 years and it was slow going. After a few weeks of slow going, I rewrote the whole thing in Typescript in a week. Not because of any general argument that TS is better, but because it’s the ecosystem I know well. Not by choice, but as a function of the jobs I’ve had.
I’d like to suggest that it’s okay to choose the tool you’re most familiar with, because you’ll move faster, write better code, and frankly web apps can be written in any of these languages.