Live data from Hacker News

Announcing TypeScript 1.0

blogs.msdn.com

21–30 of 118 posts

Re: Announcing TypeScript 1.0

#22
post #20

I am huge believer in typescript. This has made me consider html5 seriously for the first time. There are still many dark spots (hello js scope, bs standards), but with Typescript I've already built stuff I could have only done AIR in the past. I find it ironic that MSFT tried to compete with Flash with Silverlight (and failed I think), and to me, Typescript means end of the line for Flash/AS3. The language is dead e…

Huh? It just transpiles into JS...

Re: Announcing TypeScript 1.0

#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, in part due to the typing.

Re: Announcing TypeScript 1.0

#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.

Re: Announcing TypeScript 1.0

#25
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.

webstorm is also reasonable, but vs is better.

Re: Announcing TypeScript 1.0

#27
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,…

Also, compiling down to human-readable and well formatted JS has always been a priority. So it's never difficult to migrate away from typescript, since the typescript can simply be replaced by the compiler's javascript output.

IIRC, this is actually one of the main reasons they're holding off on implementing async/await, since that would require the compiler to convert functions into unreadable state machines.

Re: Announcing TypeScript 1.0

#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 said, I think that there are similar TS tools available as well)

Re: Announcing TypeScript 1.0

#29
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,…

Another feature that's not talked about much is its support for AMD and CommonJS modules. So you can easily just add an "import moduleName = require('my/module/path');" to the top of your typescript file. And you'll get full intellisense and type-checking on the referenced module in Visual Studio. This alone has made it worth using for me.

Re: Announcing TypeScript 1.0

#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 ;)
Post reply on HN