7 ms·

Why not TypeScript?

• kyrra 13y ago
  For me: because my background is mainly Java. While I understand prototype inheritance, I'm not as familiar with the programming style of Javascript. I like being able to create strict class structures and use those. Prototype structure allows for ad-hoc creation of a class. This makes code analysis and tooling a lot more difficult to do properly. (I do have to deal with the fun that is Perl on a daily basis, but I'm still more a fan of Java style OOP). Also, my entire professional career has been working on projects that are worked on by 30+ people with a very large code base. When you have large teams using a language that doesn't enforce strict structure, you tend to miss things that could have easily been found at compile-time with proper tooling. This can be accomplished in languages like Javascript, but it requires strict internal controls. Having the language give you that kind of support out of the box is nice to have.
  • recuter 13y ago
    This is a very clear and perfectly acceptable Raison d'être. It is unsurprising that Dart is by and for the same sort of people that gave us and use(d) GWT. I say godbless and godspeed, but it is very much against the grain of the web and personally I find Typescript, EC6, and projects like Angular and possibly Meteor more exciting by far. To each his own, this does fill a need. The conspiracy aficionados Dart attracts however sure are unfortunate.
  • Romoku 13y ago
    TypeScript is a typed superset of JavaScript. It has classes, interfaces, static typing, and object oriented polymorphism. TypeScript is designed to be used on larger projects.
    • tree_of_item 13y ago
      TypeScript also lets anyone ignore all of that and play cowboys and indians with prototypes.