3 ms·
> The problem with these components that they usually come > with a whole family-in-law: if you decide to go with > ExtJS’ grid, you basically have to buy
by j_s 14y ago
> The problem with these components that they usually come
> with a whole family-in-law: if you decide to go with
> ExtJS’ grid, you basically have to buy into ExtJS as a whole.
> ...
> When you enter the Dart world, a lot of choices are
> made for you. And I have come to believe that’s a good thing.
I don't understand why it's ok to pick one 'world' but not the other (though I personally disliked ExtJS too).
- spankalee 14y agoYou're right, or at least not incorrect :) If JavaScript started off with a module system, a decent core library, Promises, Classes, etc., a lot of this pain would have been avoided. But of course, part of it's beauty was that it was so simple. As these things become standardized in JS, hopefully the incompatible add-ons will fade away, but it'll take years. Dart has an advantage of a clean slate, which is why it's "ok" in a sense - once you've decided to use Dart you also get decision/opinions on a lot more.
- dfreire 14y agoExactly. It is not acceptable to buy into a large Javascript framework, but it is acceptable to buy into a whole different language? I fail to see the validity of this argument... So what if one needs to use a Javascript library? Does one wait for the community to implement the wrapper around it? Does one implement the wrapper oneself? Typescript on the other hand, seems to be more in line with the author's purposes, with one additional - and imo crucial - benefit: Javascript is valid Typescript (i.e. no need to change existing code, or wrap around libraries).