3 ms·
So, I've had to maintain (upgrade) a Node/V8 extension, an Angular1 and an Angular2+ but never stopped to understand routing. (We talked about it briefly around
by pas 9y ago
So, I've had to maintain (upgrade) a Node/V8 extension, an Angular1 and an Angular2+ but never stopped to understand routing. (We talked about it briefly around that ng1 app.) And I have no idea how Node extensions hook into V8 under the covers.
There were no abstraction breaks. C++ compiled, the thing works, the same goes for ng2 with TS. Ng1 is just plain ugly, but works fine.
I like React/JSX, FRP, I hate the size of the bundles Angular spits out, the byzantine boilerplate required to put something on screen and to make components interact, but it works, and it comes as a full package, and it keeps getting better.
The design principles of Ng are sound. Ng1 was overcomplicated. Ng2 is okay-ish.
I think ng lacks the "documentation" that the React ecosystem must provide due to its separatedness/modularity.
But my main point is, that basically good developers will compare those routing plugins/libs, and those same devs can solve problems when ng2 spits at them. And newbie frontend devs jump on the React is small and simple hype train and take the first tutorial and then get lost in that jungle. (And I'm not saying this can't happen with ng1/2, but neither codebase is about teaching programmers, so that's a very fringe aspect of this topic.)