Live data from Hacker News

Announcing TypeScript 0.9.1

blogs.msdn.com

41–50 of 116 posts

Re: Announcing TypeScript 0.9.1

#41
post #24

I sometimes find myself torn between dynamic typing (great for rapid prototyping) and static typing (great for tooling and compile-time error checks). I'm a big fan of TypeScript's approach, which gives you the best of both worlds. Start with fully dynamic code to explore the problem space, then add more static guarantees as you firm up your design. I haven't had occasion to write a big web app recently, but I'm itch…

Did I just hear someone say they were looking for a web app to write? I think he may even know something about software engineering ...

Don't everybody mob him at once :-)

Re: Announcing TypeScript 0.9.1

#42

Love how folks here love to discuss the merits/demerits of a language (not the version of the language) EVERY TIME a new version is announced. This works for every language.

Me too. But I don't agree that it works for every language.

Often the stuff that "just works" doesn't end up producing a lot of chatter on the intertubes, at least not nearly as much as something that looks seductively simple but turns out to be much harder in practice.

Another example I like is Lua: elegant, mature, and used in some very very big applications. If there was ever evidence that a codebase was high quality and nearly bug free, it's that. But when was the last time we had a good flamewar (with namecalling) over Lua?

Re: Announcing TypeScript 0.9.1

#44
post #38

I 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…

> What would make TypeScript awesome is support from more IDEs (Eclipse especially).

There exists a plugin for eclipse, but I have never tried it. I'm mostly an Intellij IDEA user.

http://marketplace.eclipse.org/content/typescript

Re: Announcing TypeScript 0.9.1

#47

I 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?

Turbulenz migrated their WebGL game engine / platform over to TypeScript and seem pretty happy with it.

Re: Announcing TypeScript 0.9.1

#48
The problem with TypeScript is its requirement for definition files which are most of the time outdated. That makes it unusable in a real project where many JS libs live together. (not saying that's the case all the time)

Re: Announcing TypeScript 0.9.1

#49
post #5

I 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?

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 :/

Re: Announcing TypeScript 0.9.1

#50
post #5

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 :/

i see people writing tests for the structure of returned objects

type annotation tests that at compile time

Post reply on HN