3 ms·

I wonder how much of the Angular growth is due to weaknesses in documentation and the relative complexity of Angular compared with alternatives. I’ve never nee

I wonder how much of the Angular growth is due to weaknesses in documentation and the relative complexity of Angular compared with alternatives. I’ve never needed to rely on SO when working with VueJS.

jordache 9y ago
That and angular is a complete framework so all aspects of a front end app would fall under the angular framework umbrella. VueJS is just a view engine. Questions related to other frameworks that work in conjunction with Vue may not be lumped together.
- aalleavitch 9y ago
  As someone who works with Angular, the vast majority of the searches I find myself doing are in the nature of "how to make X library work with Angular". It's just a massive beast with a lot of moving parts, some of them only tangentially related to use of the actual library (I find myself doing a lot of searches related to the Angular CLI, Karma tests, etc). The other thing that is frustrating is that the changes across the different versions of Angular are so dramatic that the best way to do things has changed pretty massively over time, and old versions of Angular are still employed pretty liberally by companies that don't want to have to go through the process of porting everything to newer versions. As a result there can be dozens of different ways to do the same thing and determining which is best based on your particular situation is non-trivial.
  - jordache 9y ago
    Hmm i'd say for me, a lot of searches involve how to do x within Angular. The API is so large and pretty decent. However it takes some effort to read through so I just find myself searching ad-hoc questions. What breaking changes are you referring to? Ever since it Angular 2 Final, the API has been pretty stable, I've been able to pretty seamlessly upgrade to angular 4+
    - aalleavitch 9y ago
      When I say "across versions" I'm also including AngularJS in there (the differences between them are still a major point of confusion for a lot of people). Also, while 4 doesn't introduce any breaking changes I know of, it does introduce a lot of little details that change best practices.

jordache 9y ago

That and angular is a complete framework so all aspects of a front end app would fall under the angular framework umbrella. VueJS is just a view engine. Questions related to other frameworks that work in conjunction with Vue may not be lumped together.

aalleavitch 9y ago
As someone who works with Angular, the vast majority of the searches I find myself doing are in the nature of "how to make X library work with Angular". It's just a massive beast with a lot of moving parts, some of them only tangentially related to use of the actual library (I find myself doing a lot of searches related to the Angular CLI, Karma tests, etc). The other thing that is frustrating is that the changes across the different versions of Angular are so dramatic that the best way to do things has changed pretty massively over time, and old versions of Angular are still employed pretty liberally by companies that don't want to have to go through the process of porting everything to newer versions. As a result there can be dozens of different ways to do the same thing and determining which is best based on your particular situation is non-trivial.
- jordache 9y ago
  Hmm i'd say for me, a lot of searches involve how to do x within Angular. The API is so large and pretty decent. However it takes some effort to read through so I just find myself searching ad-hoc questions. What breaking changes are you referring to? Ever since it Angular 2 Final, the API has been pretty stable, I've been able to pretty seamlessly upgrade to angular 4+
  - aalleavitch 9y ago
    When I say "across versions" I'm also including AngularJS in there (the differences between them are still a major point of confusion for a lot of people). Also, while 4 doesn't introduce any breaking changes I know of, it does introduce a lot of little details that change best practices.