Live data from Hacker News

Announcing TypeScript 1.0

blogs.msdn.com

111–118 of 118 posts

Re: Announcing TypeScript 1.0

#111
post #109
post #104

Earlier quoted context omitted.

In a typical Javascript workflow, near-instant feedback is the baseline. I really like how Facebook's Hack has a local file system monitor which incrementally compiles on file changes. I haven't used it yet, but it sounds like a nearly ideal compromise.

Typescript has a command line option for this as well. As far as I can tell, the language would also support a non-validating mode that would be more or less instantaneous (the transformations it performs are all local, and none of them involve knowledge of the types involved).

Neat, I'll need to look into that.

Re: Announcing TypeScript 1.0

#112
post #52

We've been using TypeScript for 9 months now on a large project. It's fantastic. There's now way I'll go back to pure JavaScript again. The type system just catches so many defects, and they're of the kind that are hard and boring to find (typos). Plus IntelliSense integration (including jsdoc) is great. On the downside, our project takes some time to compile so we had to build a tool to do it incrementally. Plus it…

Agreed, TypeScript is great, but the compiler is excruciatingly slow. I have to segment my app into multiple sub-build areas and only build a subset at a time, which is annoying because I frequently end up making small changes outside of that subset of code. My app is only around 25000 lines of code and a full compilation still takes around 50-60 seconds which, in a JavaScript workflow, is a lot of friction.

Strange, I'm able to compile 12k lines of code (that's output) in 5.2 seconds. Running this on a watch + autoreload process, so 6 seconds after I hit save, the results show up in my web browser. I do remember 0.9.1 being excruciatingly slow though. Edit: forgot to mention, I'm using the NPM package

Re: Announcing TypeScript 1.0

#113
post #67
post #11

Earlier quoted context omitted.

This is just a temporary limitation of asm.js because it has no access to garbage-collected data. In the future it should have support for managed languages.

Source?

> Q. Can asm.js serve as a VM for managed languages, like the JVM or CLR? A. Right now, asm.js has no direct access to garbage-collected data; an asm.js program can only interact indirectly with external data via numeric handles. In future versions we intend to introduce garbage collection and structured data based on the ES6 structured binary data API, which will make asm.js an even better target for managed languages. [1]

[1] http://asmjs.org/faq.html

Re: Announcing TypeScript 1.0

#114
I always get voted down for this, but I still feel that typescript is an answer to a question that nobody is asking. (I'm also very suspect of all of the positive comments. Is HN really this pro-MS for JavaScript?) In my company, we literally have a typescript counterpart team doing the same projects. Our code is cleaner, better architected, and our team is able to consistently produce 2 to 3 times more features. In my experience, the teams that choose typescript are usually windows devs that cannot wean themselves off of visual studio due to their dependence upon auto completion and IDE tools. I'm not hating, I just don't understand why any js dev would add code to their code.

Re: Announcing TypeScript 1.0

#116

I always get voted down for this, but I still feel that typescript is an answer to a question that nobody is asking. (I'm also very suspect of all of the positive comments. Is HN really this pro-MS for JavaScript?) In my company, we literally have a typescript counterpart team doing the same projects. Our code is cleaner, better architected, and our team is able to consistently produce 2 to 3 times more features. In…

Yep, voted down for no reason. I have actual real world experience with teams trying to use this technology. Is there an actual MS army trying to keep these threads pro MS?

Re: Announcing TypeScript 1.0

#117

I always get voted down for this, but I still feel that typescript is an answer to a question that nobody is asking. (I'm also very suspect of all of the positive comments. Is HN really this pro-MS for JavaScript?) In my company, we literally have a typescript counterpart team doing the same projects. Our code is cleaner, better architected, and our team is able to consistently produce 2 to 3 times more features. In…

> In my experience, the teams that choose typescript are usually windows devs that cannot wean themselves off of visual studio due to their dependence upon auto completion and IDE tools.

Well, since VS does auto-completion with JavaScript too, so maybe you're not understanding the whole situation. Some people like TypeScript for its ability to facilitate creation of large projects via addition types, classes, and namespaces, while retaining much of the basic JavaScript syntax.

Re: Announcing TypeScript 1.0

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

TypeScript also adds namespaces.
Post reply on HN