4 ms·
What's so good about TypeScript's type system and what problem does it solve?
by Kiro 13y ago
What's so good about TypeScript's type system and what problem does it solve?
- 10098 13y agoProblems like I look at a function and have no clue about what it's arguments are.
- tracker1 13y agoJSDoc comments?
- 727374 13y agoIn general, I believe it will help make larger JS codebases more maintainable. Specifically it enhances the following: - Refactoring e.g. easily globally change a class member's name - Type safety e.g. it will bark if you pass a string where an int is expected - General IDE handyness e.g. 'Go to definition' A really good demo here: http://channel9.msdn.com/Events/Build/2013/3-314 http://channel9.msdn.com/Events/Build/2013/3-314
- zcrar70 13y agothe two best features of Typescript's type system IMHO are: - structural typing for interfaces (which means that classes implicitly implement an interface if the definitions match) - gradual typing (mainly the ability to convert between 'any' and other types implicitly, which makes it much easier to interact with JS libraries/port JS code to Typescript.) More generally speaking, Typescript aims to solve the problem of maintaining large codebases by giving you the additional security of static typing. The idea is that many simple errors can often be caught by a compiler, but would be much more time-consuming to find otherwise.
- tracker1 13y agoJS already has this.. if (obj && obj.quack && typeof obj.quack == 'function') obj.quack(); //looks like a duck
- ilaksh 13y agoAlmost no one realizes this, but the main purpose of TypeScript is to negate one of JavaScript's greatest advantages which is the lack of typing. This is an advantage because it makes code easier to write and read. The problem that TypeScript solves is that the web platform is in direct conflict with Microsoft's monopolies in PC gaming and business productivity software (Office). Confusing developers into thinking that JavaScript needs types leads them down the path of statically typed languages, i.e. C# and Microsoft's proprietary and closed .NET Framework and software ecosystem.
- drifkin 13y agoI think optional typing is better than no typing. It's useful for allowing APIs to be self documenting. It seems as if optional typing is going to get more and more popular. For example, see Google's optional typing in dart, where they actually recommend to not use types for local variables: https://www.dartlang.org/articles/style-guide/#type-annotations https://www.dartlang.org/articles/style-guide/#type-annotati...
- ilaksh 13y agoI am not sure. I think that descriptive identifiers can indicate the type and be augmented by documentation.
- lmm 13y agoThey can. But both tend to get out of date as a codebase develops. It's very useful to have an automated tool that ensures the documentation lines up with the actual code - i.e. a type checker.
- CmonDev 13y agoThe "Open Web" is closed to one single language choice that was made for you by someone else. TypeScript is being developed, because Microsoft adapts to where the world is moving and they are just trying to avert the disaster that will happen when enterprises will actually start trying developing whole applications in JS. And Google is developing a higher-order version language as well. Nobody developed a language to run on top of Java, C#, C++, but there is a plenty of choice for JS: Dart, TypeScript, CoffeeScript etc.