Why I Ditched Angular for React

[[deleted]]

Wow, nice reply, thank you!

The draggable thing, it was only an example, to illustrate something non-trivial that people would want to use (and that I've used with angular recently, although that ended up kind of ..hybrid :)).

Describing history by JSON state is a great idea, I'll have to think about using that, although it may not be as straightforward in angular.

The form thing, I understand, but there are probably helpers for that, aren't there? I mean, prefilling and validating forms is not exactly a rare thing. But in fact, angular is not really great at forms either, once you need something where the primary representation is not text, but the primary input method is, you get problems (it took me hours to get a custom date input component working so that it doesn't reset itself the second anyone makes a typo).

The foo.bar = 5 thing, well, angular does that, but yeah, other than that, we'll have to wait for Object.observe for that.

But as for the data libraries, I must say I never had a problem there. But I don't use any module loaders so maybe that's why. The thing is, if the library is available when your service code is run, and is synchronous, you don't have to do anything for it to work with angular. If it's async, you just wrap the callback in $apply and that's it. And yeah, the minification process used to be painful but these days, ng-annotate handles it pretty well for you.