I also use a lot of these points when I explain why I use NodeJS and avoid typescript for most of my projects.
The thing is though, it really depends on the project.
Most of my projects are web UI heavy with simple commodity CRUD RESTful APIs sprinkled with business logic.
Time to market tends to be the biggest constraint (I live in startup world), so "good enough" performance and a loose type system are perfect for that.
If I was writing SCADA controllers for a nuclear power plant, my choice of technology would be much different.
The sorts of "rah rah" debates we have on HN about languages frequently don't take the specific project characteristics into account.
Like with everything, it boils down to intelligently selecting the right tool for the job.
I also use a lot of these points when I explain why I use NodeJS and avoid typescript for most of my projects.
The thing is though, it really depends on the project.
Most of my projects are web UI heavy with simple commodity CRUD RESTful APIs sprinkled with business logic.
Time to market tends to be the biggest constraint (I live in startup world), so "good enough" performance and a loose type system are perfect for that.
If I was writing SCADA controllers for a nuclear power plant, my choice of technology would be much different.
The sorts of "rah rah" debates we have on HN about languages frequently don't take the specific project characteristics into account.
Like with everything, it boils down to intelligently selecting the right tool for the job.