3 ms·
Came here to say this. In the last slide, when they were piling "RIP Directives", "RIP DI", "RIP Modules", etc., the only thing I had in mind was "RIP Angular".
by rdsubhas 12y ago
Came here to say this. In the last slide, when they were piling "RIP Directives", "RIP DI", "RIP Modules", etc., the only thing I had in mind was "RIP Angular". Very disappointing.
- GhotiFish 12y agoReally? Because I found angular to be highly convoluted in practice (and I have implemented it in practice). Most of my team eventually settled on the conclusion that "the cognitive load of working through the implications of how these nested directives play out in an application is simply not worth it". Or something to that effect. We all studied angular studiously, we all did our best to implement it in an effective and sound manner, and when things went wrong, and they always go wrong, the shear complexity of the framework tied our hands and forced us to do some very ugly hacks. I look at our application as it stands, and I regret using angular. If angular 2 is simplifying it's framework, the only thing I have to say to that is "Thank god, maybe I'll try it again"