5 ms·
You might like working in GWT or Dart better then. I for one quite like being able to mix in other objects but exclude some properties/methods while still unde
by mtrimpe 14y ago
You might like working in GWT or Dart better then.
I for one quite like being able to mix in other objects but exclude some properties/methods while still understanding what's actually happening under the hood without needing a Haskell-level type system.
- coldtea 14y ago>You might like working in GWT or Dart better then. Because one single feature (the above offering native classes) trumps stuff like browser support, libraries, or awkward development environment etc, right? Or he could continue to work with JS, with a class based system, either ad-hoc (as 99% of JS developers use), or built in ES6.
- mtrimpe 14y agoWe were talking about swimming against the stream or not. In those two languages the author's preferred programming style would be considered going with the stream. ES6 sounds great since it would offer the best of both worlds, but it's going to take quite a while before you'll be able to do your everyday development in ES6.
- coldtea 14y ago>We were talking about swimming against the stream or not. In those two languages the author's preferred programming style would be considered going with the stream. Yes, but then you have to swim against other streams, like the languages not being mainstream, needing a translation layer ton run in the browser, etc etc.