3 ms·

I'm not making any value judgment here; I dislike React and it's over-abstraction paradigm. I long for the days when web components will be mature enough that w

by Touche 10y ago

I'm not making any value judgment here; I dislike React and it's over-abstraction paradigm. I long for the days when web components will be mature enough that we can leave frameworks behind. But there's no denying that if you go to a web/js meetup in just about any city in the US 8/10 talks will have something to do with React, and that's the position Angular was in 3 years ago. Doing silly things like maintain 2 frameworks with the same name isn't going to help.

filiph 10y ago
FWIW, I don't think number of talks on meetups is a good measure of long-term success at all. AngularDart's play is not to be the next React (the same way Go is not trying to be the next PHP). AngularDart users at Google are, to my knowledge, extremely happy with the framework, but their enthusiasm won't necessarily (or even probably) translate to large portions of JS crowd. AngularDart works for a specific set of problems (very large web apps that need to be performant and work well on mobile, built mostly by developers with classic CS background). I personally think insisting on the one framework (Dart+JS+TS) was the silly thing to do, and I'm glad that's over.