What I'd like is a language I can use that has optional typing where all the libraries follow a strict type system but the application I put on top of it doesn't care.
That is the exact opposite of what I get with TypeScript. I'm left with a lot of dynamic mess libraries that I build my typed application on top of.
Steel on top of jello.
I think you should start laying off HN, in all honesty.
chortle
Not so long ago they were saying the same about Ruby, and Java before that, and so on down a long and winding history of ludicrous one-language-swallows-the-world predictions.
In this case it's not so much a prediction as an observation of what has already been happening.
It's everywhere at this point.
I'm starting to think theres a JS Bubble forming, inside which people who only ever touch JS and nothing else proclaim that the world and the moon are made entirely of JavaScript.
Stripped down, functional C with type inference? Yes, please.
Javascript is the C++ of web dev. You bolt a ton of things on top of a shitty language and you hope to obtain a slice of it that is decent in the long run. Except it's still going to be full of terrible quirks and 30 ways to shoot yourself.
I'm sorry, but I don't want this future for programming.
Shitty date/time implementations (unless you're using moment)
Callback hell?
That's just my list for this morning.
Don't know what you mean by this. As for the other things; like I said, getting first class functions right makes those other things unimportant. Are you running into the problems with DateTime that often? I can't even remember what those problems are. I don't doubt they exist, but I think you're over-inflating the importance.
But yeah, if you absolutely want a dynamic language, you have much saner choices with a considerably more robust ecosystem (hello Python).
> I'm sorry, but I don't want this future for programming.
I don't want this present either :)