How do you think does it fit in with ES6? I feel like we're coming to a point in time where there should be a major shift in how we write javascript in a modern way -- so far my thought process has been that Coffescript is a nice stopgap before ES6 and the dust has almost settled enough to write ES6 first sorta..
Bit of a ramble. Interesting times.
https://github.com/tomsdev/brackets-typescript-code-intel
Still early
TypeScript is entirely different thing. It adds a layer of static analysis to the language, which does not end in the code that actually runs. Generally everything you type in Coffee has an equivalent in compiled JS; it is not so with TypeScript, where you can write pages of code which won't be visible in the compiled JS.
CS and TS have different goals and are different things, and the only thing they have in common is that they both "transpile"/compile some language to another. Hardly a similarity that makes them very close.
Actually I would appreciate TypeScript implementation on top of Coffee (or the other way around, whichever would be simpler). There is a dialect of CS that supports contracts (you really, really should start using contracts anyway), but that's yet another thing that cannot hope to replace static verification of certain things in programs.
Btw, TypeScript also aiming to fix context problem so in callbacks 'this' keyword is always related to parent class.
Btw, based on typescript discussions, they are going to implement async/await functionality too.
I was primarily a curly-brace developer for 10 years, but changed my mind after a few years of Python, Ruby and Lua. Now I actually think these languages look better than the curly-brace family.
A programming language works with a text editor? Wow!
It is running on Linux/Mac/Windows (node.js module).
And already has support in all major IDE (Visual Studio, IntelliJ) and text editors (Sublime, Emacs, ..)
I appreciate the effort, (I can't say the same for other Microsoft projects), but it's still not fun to play with typescript in emacs (as opposed to more mature projects like Python, C or, of course, Lisp).
Pretty much everyone came out impressed. Typescript is just JS with type hints, and neat warnings if you send a function something which its signature doesn't expect.
You can make a JS project a Typescript one immediately, adding type hints as you go, which for large projects is damn useful. The output, however, is pure regular old JS.
It's just like a CSS preprocessor, but for JS - transparently adding some optional awesomeness.
It works on Linux/Mac and SublimeText (albeit you don't get all the VS Intellisense stuff IIRC) too. I'm looking forward to trying it on a new project.