| The funny thing about lists of features is that they tend to create their own focus illusion. Here's what I want to know: 1) Are the various abstractions surrounding those things reasonably legible? Or are we back to talking about Factory Service Providers again or otherwise importing other bits of pattern hell idioms into a language where there's always been easier ways to get things done? 1a) What did they do to make scope legibility better? (Assuming we still have the same scoping concept) 2) Do the abstractions leak? Angular 1.x abstractions leak like hell. Even if you're not concerned about performance, you have to be careful about snakes breaking out from under them and providing unexpected behavior, if you are concerned about performance you'd better have a detailed understanding about how the digest cycle works and it's utterly laughable that people thought this was a reasonable tradeoff for two-way data binding. 3) Is the tooling better? Some versions of Batarang were just straight up broken. Given that Angular 2 isn't really stable yet, I have my doubts these questions can have clear answers, but happy to receive surprise illumination. (At the moment, though, still avoiding applying to work at anywhere that lists Angular as a requirement. There's going to be technical debt and likely enough an ongoing technical decision making deficit at anywhere that does.) |
It all feels way too abstract and way too much "it's own thing" that is quite separate from the world of HTML and Javascript.