Live data from Hacker News

Announcing TypeScript 1.0

blogs.msdn.com

31–40 of 118 posts

Re: Announcing TypeScript 1.0

#31
post #28

Could someone be so kind as to explain why I should consider Typescript over Coffeescript in future projects? I've been using CS for the past year or two, but I'm hearing a lot of buzz around TS for the past few months. It would be really nice to have a better idea as to why it should be best to move now - is it really that much better? (I love the CS tools available on PyCharm; they really made my life easier. That…

Coffee is to Type Script what indentation is to type theory.

Re: Announcing TypeScript 1.0

#32
post #28

Could someone be so kind as to explain why I should consider Typescript over Coffeescript in future projects? I've been using CS for the past year or two, but I'm hearing a lot of buzz around TS for the past few months. It would be really nice to have a better idea as to why it should be best to move now - is it really that much better? (I love the CS tools available on PyCharm; they really made my life easier. That…

Typescript is just a superset of JS, what does that mean?

Is just your regular js, but with some stuff added like type

check, classes, interfaces and some cute operators, just the

language that most know with some goodies added to help

with development, that is and that all, in oppose to CS that

is just syntatic sugar with others cute tricks that make the

language more appealing to people like you (assuming by your

post that you are a python developer). So if you are into JS

or type check then you should give TS a try, if not then

just stick with CS, only you can answer is changing

transpiler in your workflow is gonna make your life easier.

Re: Announcing TypeScript 1.0

#33
post #30
post #28

Could someone be so kind as to explain why I should consider Typescript over Coffeescript in future projects? I've been using CS for the past year or two, but I'm hearing a lot of buzz around TS for the past few months. It would be really nice to have a better idea as to why it should be best to move now - is it really that much better? (I love the CS tools available on PyCharm; they really made my life easier. That…

Maybe I'm just waiting for TypeCoffeeScript ;)

There is actualy one already: https://www.npmjs.org/package/typed-coffee-script

Re: Announcing TypeScript 1.0

#34
post #18

Anders is my favourite language designer, ever :) TypeScript is something I'm still trying to get more buy-in from my team, but the issue is the lack of decent autocomplete/static analysis in anything other than Visual Studio. I'm working on that problem myself, actually.

IntelliJ supports TypeScript! http://www.jetbrains.com/idea/webhelp/typescript-support.htm...

Re: Announcing TypeScript 1.0

#35
post #24
post #18

Anders is my favourite language designer, ever :) TypeScript is something I'm still trying to get more buy-in from my team, but the issue is the lack of decent autocomplete/static analysis in anything other than Visual Studio. I'm working on that problem myself, actually.

I use Cats IDE on a relatively large project and find it very good.

I set up Cats but I found it was super buggy under Linux Mint :(

Re: Announcing TypeScript 1.0

#36
post #28

Could someone be so kind as to explain why I should consider Typescript over Coffeescript in future projects? I've been using CS for the past year or two, but I'm hearing a lot of buzz around TS for the past few months. It would be really nice to have a better idea as to why it should be best to move now - is it really that much better? (I love the CS tools available on PyCharm; they really made my life easier. That…

One reason (as I see it) is that TypeScript is implementing ES6 features along with the type-specifc stuff, so it's going to end up in a place where it's very compatible with the 'future' of JavaScript.

CoffeeScript will always be something quite different. I love it, but that difference makes me nervous. ES6 ought to bring a lot of the features I like about CoffeeScript into JavaScript.

Re: Announcing TypeScript 1.0

#37
The typescript playground[1], which lets you try TypeScript in your browser, looks so professional and finished when compared to CoffeeScript[2] or Dart[3]. As someone who attempted a half-baked Rust to JavaScript transpiler[4], I am floored with the packaging of TypeScript (tutorials, specs, editor integrations, npm, playground). At the moment, the only missing feature that my jealousy could point out is autoscrolling (see lexer example in my demo)!

By the way, is playground using v1.0?

[1] http://www.typescriptlang.org/Playground/

[2] http://coffeescript.org/ (Try CoffeeScript tab)

[3] http://try.dartlang.org/

[4] http://bilalhusain.com/rust-lexer/syntax.html

Re: Announcing TypeScript 1.0

#38
post #18

Anders is my favourite language designer, ever :) TypeScript is something I'm still trying to get more buy-in from my team, but the issue is the lack of decent autocomplete/static analysis in anything other than Visual Studio. I'm working on that problem myself, actually.

I've had autocomplete with Eclipse, WebStorm and Sublime.

Re: Announcing TypeScript 1.0

#39
post #23
post #21

The article is light on 'What is Typescript'. Can someone explain what TypeScript is?

It's a compile-to-JavaScript language, like CoffeeScript. Differentiating features: - Strict superset of JS. All(?) JS is valid TS, making it easier to migrate to TS. - Many of the added features are from EcmaScript 6, i.e. JavaScript Of The Future. TS lets you use those today, instead of waiting for browsers to implement. - (Optional) type system, which some people are fans of. - Much stronger tooling & IDE support,…

Not all valid JavaScript is valid TypeScript, e.g. you can't use undeclared variables. The compiler can still output the .js file, though.

Re: Announcing TypeScript 1.0

#40
The language is nice, but the compiler uses its own lib.d.ts which has all sorts of definitions for browsers and even proprietary MSIE ones. This doesn't make any sense when using TypeScript in any other context (like Gjs, NodeJS, Rhino, Seed, etc.). TypeScript shouldn't assume a browser by default, or at least provide an option for compiling without lib.d.ts.
Post reply on HN