TypeScript takes an afternoon to learn, and is strongly typed JavaScrupt. It's not perfect, but it's really very good. The JS produced is predictable, clean, and makes sense with virtually zero overhead.
Typescript can't guess types with libraries that are not written in Typescript. That's not the solution. But maybe that's the best you'll ever get in the JS world.
TypeScript as of today is supported by a total of zero browsers with zero planned to add support in the near future. It doesn't replaces JavaScript in any way, just builds a larger house on the sand.
You don't know anything about TypeScript, yet you choose to weigh in on it. Interesting. I think you must be confusing TypeScript with something else, like Dart maybe?
Please clarify what I said that was incorrect? I said that TypeScript doesn't have browser support (true) and that they have no plans to add browser support (true), and I added that TypeScript is like building a house on sand (i.e. it is all built on top of JavaScript, since there is no browser support for TypeScript).
Please, go ahead, and correct my ignorance. Since I don't know anything...
The stated goal of TypeScript was never to run in the browser. That's what confused me about your statement and made me wonder if you were confusing it with Dart. TypeScript wraps JavaScript with static type checking and some other useful contructs. It compiles to very clean and readable JavaScript. It's a tool, not a browser script.
