The awkward DI/module system, I'm fine with loosing that. The router I will probably miss, but there are decent router components for react. Services, factori

The awkward DI/module system, I'm fine with loosing that. The router I will probably miss, but there are decent router components for react. Services, factories and providers? Rather big words for some insignificant differences. The only thing I'll really miss is simple data-binding - but it has too high of a performance cost anyway. Simpler server-side rendering and testing will more than make up for that. Looking at directives vs react components, it seems like many Angular features are just workarounds for some of its design choices. What bugs me the most is the cognitive dissonance caused by what I'm reading about the new Angular. Its supposed to be more modular. Yet the thinking shown on these slides is quite the opposite: * it introduces attribute changes in the markup that seem disharmonious with CSS selector syntax. * it now also coupled with a new language in order to be used sensibly, which reintroduces annotations - another language-in-language that may lack the proper design care to make it composable and usable (e.g. how do you combine 5 annotations into one? I have no idea, guess you'll have to copy-paste them) In short, to me it seems like Angular 2.0 is intent on going forward with adding even more complexity while breaking backward compatibility. "More modular" is not what I'm seeing here at all.