Most languages in use today were developed for different purposes than what they are primarily used for today. That's a non argument unless it has significantly worse time dealing with it's past than it's competition which is debatable, but definitely not objectively true.

Everything else means, you have to learn two different languages with two different syntaxes. sets of quirks and exceptions, that you have to maintain two different codebases that cannot share any code (like types for instance) (specific exceptions aside), you cannot have type safe data from http requests, you can't leverage the largest and simultaneously fastest growing ecosystem of today...

I am not saying js (ts) is always the best choice, just that sometimes it actually is.

Reply to this note

Please Login to reply.

Discussion

If it's more convenient and seems to work, why not?

I'm not trying to set up any purity tests, it's mostly a meme.

I wouldn't use python (even with type checking) in prod but I understand different people will make different choices.

That last sentence is the key. I for instance pretty much reverted to TS entirely despite previously kind of hating on it. Some people would not touch it with a 6' pole and that's ok. I wouldn't touch Java or Python for instance, but you'll never find me hating on people that use it or those languages themselves.