News for hackers. Stuff that matters.
Re:Why does TypeScript have be the answer to anything? by ajanuary on Tuesday October 02, 2012 @11:11AM (#4602365)
The type system in TypeScript isn't 'rigid'. It's both optional and structural. These combine to make it a heck of a lot more lightweight than something like C++ or Java.

The classes in TypeScript are a formalisation of a very common design pattern in Javascript, so obviously people do think it's useful. TypeScript takes the common practice and makes it more succinct. (Other than inheritance, which does seem a little un-JSy)

Re:Why does TypeScript have be the answer to anything? by zachrose on Tuesday October 02, 2012 @02:40PM (#4603523)
Perhaps you understand TypeScript better than I do. My rough understanding is that TypeScript is JavaScript with what's essentially inline JSDoc. The compiler is just there to give hints and warnings. Is this right?
Re:Why does TypeScript have be the answer to anything? by Locke1689 on Wednesday October 03, 2012 @02:07AM (#4606071)
No. JSDoc is just hints. TypeScript offers a fuzzy type unification system.