3 ms·
The problem it's trying to solve is that Google's JavaScript optimizing team is hitting the limits of what they can do to speed the language up given the constr
by rtfeldman 13y ago
The problem it's trying to solve is that Google's JavaScript optimizing team is hitting the limits of what they can do to speed the language up given the constraints imposed by JS.
They want a replacement language that's more optimization-friendly so that they can continue pushing for faster Web clients.
Given this creator goal, and most programmers' goals of "use a language that better suits my needs," it's not terribly surprising that Dart hasn't seen the kind of community interest that CoffeeScript has.
- spankalee 13y agoThat's not the only problem Dart is trying to solve. Productivity and the ability to build good tools for the language are huge factors in Dart's design. That's why it has libraries, type annotations, a declarative top-level structure, and some of the reason for closed objects. Good tools for Dart are _much_ easier to write than tools for a very dynamic language.