My best guess is that Ember is marketed as "omg look awesome!" and Angular is marketed as "hey, this is useful", and this causes the user community compositions to differ just enough for this to be the case (though there are still crazed fanboys on both sides, hence the Ember<->Angular comment thread wars).
This is not even wrong...it's just an absurd statement. Using angular makes it no easier or more difficult for Google "to collect data and increase advertising revenue" compared to any other JS framework.
I am surprised by these threads too, and in general the ember vs angular turf wars. Maybe it's just that I don't work with this sort of thing often, but to me they look strikingly similar.
I'm trying to come up with similar software schisms: vi vs emacs? GNOME vs KDE? Linux vs BSD? C vs C++? C++ vs ObjC? All of these differences sound more substantive to me.
Well, Angular and Ember actually do have substantial differences - they have surprisingly different architectures and general philosophies driving them.
Unfortunately, that seems to lead to a lot of acrimony between them. I wonder if a big part of it is that each side is convinced there won't be space for both in the future, and that a clear winner has to be declared - which I don't think is true at all. This town is certainly big enough for the both of them :)
As for drama within the Ember community itself, that's a little more complex. I think a big part of it is that Ember seems to have a lower barrier to entry than Angular at first glance, but certainly has its own catches and hang-ups, and running into those when you thought you had found a holy grail can be extremely frustrating.
He's probably upset at investing in a pre-1.0 software (apparently he spent "weeks" making pagination work) and then finding out -- gasp! -- it isn't completely stable yet.
