2.0 was much more intuitive to me when I tried it 6 months ago. Now I don't see why someone would choose angular 2 over react, but I also don't see why someone would start a new application in Angular 1 either.
I agree. As someone who never used 1.x in anger I found 2.x much more intuitive on those occasions I had to pore through some 1.x code. 2.x does have its oddities though.
I've used Vue quite a bit, but I've found that Angular has more feature out of the box (ability to define custom sync and async validators, and other misc things). While I prefer Vue's simplicity and API, it's just not as feature complete.
Idk, I liked the quickstart. It's not great if you just want a really simple example of how to use it, but it does a great job of showing off how many different features angular2 supports and how easy it is to use them.
As a big fan of Angular 2, Angular 1 is fucking complete garbage.
A large scale enterprise framework shouldn't be picked because it's "easy." Writing vanilla PHP is easy, but that doesn't mean I'll choose it for a high scale application.
Angular 1 has awful design and it is insanely slow. The only real reason it's popular is because it allows for much easier and dirtier code than other frameworks. This makes it insanely popular with beginners and people in developing countries who don't know any better.
Angular 2 focuses on improving the scale and maintenance of Angular applications, so it makes sense they have had to sacrifice some of the simplicity for a more rigid structure. React does the same thing, but with far more abstract means.
Angular2 itself is actually pretty simple to understand. The build/setup process was a bit more convoluted than v1, but that is why Google built the CLI tool.
The "copy this into there" seems weird, why not include it in the/some CLI to do it automatically. Its not even that hard.
But yeah, i also struggled a while ago. Especially integrating typescript with my existing Gulp stuff was a mess (also had to include a custom existing plugin that was created for jquery but worked fine in angular1.
However my main issue with this is that everything has to start from scratch. Many modules need to be ported (and completely refactored as well) and you will run into many issues that aren't easily found in Google or whatever. Plus editors can't really understand everything. And so on.
10
u/ataskitasovado Sep 15 '16
Now that version 1.x has got so much traction I think new projects will still consider 1.x over 2.0.