What are the limitations of the type checker? i.e. does the compiler fully have your back, or are we just talking validating whether or not a method param takes a String vs. an Int?
Coffee is a dream [for me], JavaScript, not so much.
What are the limitations of the type checker? i.e. does the compiler fully have your back, or are we just talking validating whether or not a method param takes a String vs. an Int?
Coffee is a dream [for me], JavaScript, not so much.
If IDE support is getting to the point where you can hover-view/click-through to type, then that is really quite impressive.
Will be awhile before that gets to MonoDevelop, however (Linux workstation here).
For me the ideal would be a terse syntax a la coffeescript, but with static type checking.
I wonder what compile times are like for large-ish TypeScript projects? Imagine it's fairly quick, but even simple static type checking will bring some overhead.
Like this? http://i.imgur.com/RRFq0dl.png
Compile times are easily control by breaking the files up. Similar to C# partial class, they can still go in the same module. I'm using the free Visual Studio Express for Web, so I'm not sure about Mono/Linux support, but I hear there is WebStorm and Sublime Text plugin support and one I also like which is Adobe Brackets.
But aside from that, the most useful feature of typescript to me has been the productivity gains, just checkout: http://www.typescriptlang.org/Playground/ You can now have an IDE that provides useful information about clases/objects/etc. (imagine if javascript actually had proper codecompletion and intellisense)