3 ms·
To me Angular2 is not really worth it. The magic was on Angular-1. It did good but now Polymer and React have the mojo each for different reasons. Unfortunately
by themihai 10y ago
To me Angular2 is not really worth it. The magic was on Angular-1. It did good but now Polymer and React have the mojo each for different reasons. Unfortunately the web development is still a big mess even on new projects with supoort for latest browsers only.
- pluma 10y agoAngular1's USP was basically the magic that turned out to be a bad idea and was removed or at least significantly reduced in Angular2: scopes and dependency injection. I can still see the appeal of Angular2 to non-JS developers (e.g. C# or Java developers switching to JS) but it's a very different framework. It's certainly no longer living up to its original claim "designers can write code without being programmers" (though that was only ever really advisable for prototypes to begin with). One of the most frequent criticisms I have heard from JS developers about Angular is that being a good JS developer and being a good Angular developer are separate pairs of shoes (compared to e.g. React+Redux where most of the learning curve is JS rather than React or Redux). I don't see Angular 2 having done anything to change that.
- cname 10y agoHaving written a handful of apps using Angular 1, I would say it's true that you have to learn Angular's way of doing things, but most of the code for the apps I've written is plain JS. Angular 2 no longer has its own module system, so that's one less Angular-specific thing you have to learn about.