Static types are attractive to me. I haven't tried Typescript for other reasons: 1) I use CoffeeScript for the concise code, which Typescript doesn't have. The

Static types are attractive to me. I haven't tried Typescript for other reasons: 1) I use CoffeeScript for the concise code, which Typescript doesn't have. The trade is a lot of verbosity for static types - verbosity above the static type declarations. 2) I don't know much about Typescript's type inference system, especially how it will develop. Not well documented, no vision. (Clojure's vision is one that I would consider exemplar.) 3) Suppose there are cases where Typescript is more appropriate. I don't know whether it is easy to expose functions to normal Javascript (while retaining types). Typed subsets of a language have often been problematic to expose to untyped parts of a language when more powerful inferences are being used (e.g. Typed Racket doesn't play well with Racket Macros). Especially if you want to pass typed => untyped => typed. 4) There's a cost to learning a new language. There's an overhead to remember an additional language. 5) Chances are, someone else is going to try it. Someone who actually has a good use case. If I wait, maybe they will talk/blog about it, and I can make a more informed decision later. I haven't been persuaded to try Typescript in a substantial piece of code. The blog posts, they don't really address the issues of concern to me. Not yet.