So assuming you are looking for a language that scales codebase size easier, why would you choose TypeScript over Dart? Dart has been baking longer, has a more holistic view of the problem, and solves a bunch of other WTFs in the language. I don’t think the subset of people doing JS that want this are big enough to support fracturing, and Dart is so obviously a better solution then this, it is very hard to see it getting anywhere
TypeScript supports more editors, and key editors at that. http://blogs.msdn.com/b/interoperability/archive/2012/10/01/sublime-text-vi-emacs-typescript-enabled.aspx
Dart supports the Dart editor and the jetbrains editors.
Both languages are fully open source. Typescript uses Git. Dart uses Subversion.
I haven’t used either, but I personally am more inclined to try TypeScript due to the editor support and because I’m assuming it will have a smaller learning curve than Dart.
From what I understand, both are optionally typed (meaning you don’t have to use type annotations, but if you do they will be checked at compile time and ignored at runtime)
The reason typescript has more editor support is because it doesn’t go as far, which is basically what I was trying to say — If you are going to make the jump to a pre-processor, that why not use the thing that is more fleshed out? If all you want is type annotations, why not use the google closure compiler which gives you that without having to go to a pre-processor?
I had never used the google closure compiler so i played with it a little after reading your comment. The compression is great but I found it to be pretty opinionated. It also requires annotations for type checking which TypeScript does automatically.
It’d be interesting to see a side by side comparison of the various options. I’m going to put that on my list of “good ideas for a blog post” (which is already filled with lots of out-dated never completed ideas.)