Earlier quoted context omitted.
My project isn't huge, but larger than it could have been using idiomatic javascript. The scoping with modules and the typing really helped since I'm familiar with C# and having "everything light up" in the IDE. Saved a ton of time letting a compiler catch things instead of writing tests. I tried coffee script, but found the copy/paste option for javascript that I have already written won me over.
Saved a ton of time letting a compiler catch things instead of writing tests. Types should never mean writing less tests :/
Announcing TypeScript 0.9.1
51–60 of 116 posts
Re: Announcing TypeScript 0.9.1
#52I haven't heard much about TypeScript since its original announce. Are any big projects using it? Does anybody have some commentary on their experience using it and where they think the project is going?
I was writing a biggish weekend project. It was mostly client-side logic with a FireBase backend. I developed the first prototype in pure JS and there were some bugs (due to me being new to this FireBase model, and some hastily developed code). I then converted the whole thing to TypeScript, because I prefer static typing. It took some time to setup: upgrading to the latest nodejs, collecting all type definitions for…
Re: Announcing TypeScript 0.9.1
#53I haven't heard much about TypeScript since its original announce. Are any big projects using it? Does anybody have some commentary on their experience using it and where they think the project is going?
Re: Announcing TypeScript 0.9.1
#54Does anyone have experience with using TypeScript with existing libraries like Angular.js? I know that there are definition files for it [1] (and many other popular libraries), but unfortunately I haven't had the time to check out their quality. [1] https://github.com/borisyankov/DefinitelyTyped/tree/master/a...
Re: Announcing TypeScript 0.9.1
#55Am justing waiting for them to implement "await".
I think you might be waiting for awhile unfortunately. Implementing await would result in a lot of autogenerated code. Typescript is largely meant to be almost 1:1 with the Javascript it produces. Anders talks about that problem in this video: http://channel9.msdn.com/Events/Build/2013/9-006
Re: Announcing TypeScript 0.9.1
#56Re: Announcing TypeScript 0.9.1
#57Earlier quoted context omitted.
Saved a ton of time letting a compiler catch things instead of writing tests. Types should never mean writing less tests :/
Static typing means automatic language-integrated type-checking unit tests. I would bet a lot of dynamic language unit testing has to do with compensating for the lack of proper type checking. It's just like using patterns compensates for lacking language features.
Re: Announcing TypeScript 0.9.1
#58Earlier quoted context omitted.
Saved a ton of time letting a compiler catch things instead of writing tests. Types should never mean writing less tests :/
i see people writing tests for the structure of returned objects type annotation tests that at compile time
There might be some worth in checking the structure of an object (including attached functions) as it leaves a public api, especially in a language like Javascript that plays it so fast and loose with object construction.
That's one of the nice thing about typescript - you can use it where it's most helpful and leave it where it's not.
Re: Announcing TypeScript 0.9.1
#59I haven't heard much about TypeScript since its original announce. Are any big projects using it? Does anybody have some commentary on their experience using it and where they think the project is going?
The largest project I know using it from what anders has mentioned is xbox music, which is about half a million lines of typescript. In addition the IE11 debugger also is written in typescript.
Re: Announcing TypeScript 0.9.1
#60I haven't heard much about TypeScript since its original announce. Are any big projects using it? Does anybody have some commentary on their experience using it and where they think the project is going?