Some Nokia devices (for one example I know of: no doubt there exist other cameras and camera phones that do something similar) have a higher resolution CCD than they need for unzoomed images and use the extra resolution for noise reduction and such when scaling the image down to the final size - so with zoom you genuinely get more detail but possibly at the expense of extra signal noise.
We are having the same discussions, and a lot of the developers seem to lean towards angular, simply because of that momentum that you mentioned.
> "The project I'm working on at Netflix is extremely ambitious, ... solving pretty interesting problems in Ember, that are actually a lot more complicated than problems I solved in previous Angular projects"
This is a key point that I keep running into. It seems that more complicated applications can benefit from Ember's very opinionated nature and more backbone-like structure...
I could be totally off base, as I've not created a large-scale app in either of these frameworks (yet).
We have a very complex Ember app, the discussion we have is largely around whether we've made the right choice.
My personal view is that we could get rid of every single problem we have with Ember if we replaced it with Angular... And instead have a whole new set of Angular problems.
You may not use an octocat, created by GitHub or by you, for products or merchandise without written permission from GitHub. This includes, but is not limited to t-shirts, toys, stickers, etc.