The problem is right there in your response. Do I do TypeScript or Facebook's flow (whatever that is, I don't know)? Or perhaps CoffeeScript? Or wait, that o

The problem is right there in your response. Do I do TypeScript or Facebook's flow (whatever that is, I don't know)? Or perhaps CoffeeScript? Or wait, that one is not typed. Or is it? Lots of people like it though! Except the ones that perfer EcmaScript 2015. Because it is the future. At least for the next 2 weeks when 2016 starts. But EcmaScript 2015 is not typed either. So much for your promise of all serious JS shops doing typed JS in next 12 months. Also, yeah, great, "serious" shops will be typed. What about "not serious" shops? They don't count? And their users who have to suffer through crappy products built using incomplete tools don't count? Oh, and you know what all these half a dozen most popular and legion of less popular solutions to the problem of "JavaScript sucks" have in common? They add yet another step into the toolchain making the developer's life so much harder. It is nobody's fault that we are were we are, but please, let's call it as it is and not pretend that this pathetic situation is somehow progress or even acceptable.