3 ms·

> The home of a peculiarly minded 21! year old web developer This developer was dropped into a larger project. He caught up with Angular 2 and TypeScript. He w

> The home of a peculiarly minded 21! year old web developer This developer was dropped into a larger project. He caught up with Angular 2 and TypeScript. He wrote an elaborate post. But maybe he had not been exposed to a larger set of diverse use cases and software patterns in practice yet. There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1. Documentation could be better of course. Moving from 1 to 2 requires a bit of unlearning, it is essentially a new framework.

Udik 10y ago
> There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1 I really don't understand how people can claim this. I got my first basic application running in angular 1 in about two hours- no, I'm not talking about a tutorial but a small, real application. All you had to do to start was to include the minified angular framework in the page and write some plain javascript functions. That's it. Now, I've been working with angular 2 for the past month or so (on a brand new application). I still have very little understanding of what the framework does or how it works. I found it pretty easy to understand the basic concepts and inner working of angular 1, but I still haven't managed to grasp what angular 2 actually does. Some things seem to work, some others just don't. The documentation is obscure and lacking. The requests for basic features or bug fixes have discussion trails that go from many months ago up to yesterday. I just googled for the first example that comes to my mind- a pretty fundamental question: what's the execution order of directives in angular 2 and how to influence it? On the first page of results, only the first two are relevant (thanks Google!). Both are StackOverflow questions, and the answers are: >As far as I know the order of execution is undefined. You shouldn't depend on a specific order. >> That's just awful.. ---- > I think priority concept is yet not there in Angular2. (If it is already i'm not aware of it yet) but One should not depend on a specific order as already said. ---- > Suppose you have ngIf and ngFor directives on one element >> that's not supported. For more details see ngIf and ngFor on same element causing error. At least for this case there is no requirement to specify an execution order. Thank god. It breaks so it doesn't even need the feature.

Udik 10y ago

> There are some learning hurdles to Angular 2 but imho. they are lower than what was there with Angular 1 I really don't understand how people can claim this. I got my first basic application running in angular 1 in about two hours- no, I'm not talking about a tutorial but a small, real application. All you had to do to start was to include the minified angular framework in the page and write some plain javascript functions. That's it. Now, I've been working with angular 2 for the past month or so (on a brand new application). I still have very little understanding of what the framework does or how it works. I found it pretty easy to understand the basic concepts and inner working of angular 1, but I still haven't managed to grasp what angular 2 actually does. Some things seem to work, some others just don't. The documentation is obscure and lacking. The requests for basic features or bug fixes have discussion trails that go from many months ago up to yesterday. I just googled for the first example that comes to my mind- a pretty fundamental question: what's the execution order of directives in angular 2 and how to influence it? On the first page of results, only the first two are relevant (thanks Google!). Both are StackOverflow questions, and the answers are: >As far as I know the order of execution is undefined. You shouldn't depend on a specific order. >> That's just awful.. ---- > I think priority concept is yet not there in Angular2. (If it is already i'm not aware of it yet) but One should not depend on a specific order as already said. ---- > Suppose you have ngIf and ngFor directives on one element >> that's not supported. For more details see ngIf and ngFor on same element causing error. At least for this case there is no requirement to specify an execution order. Thank god. It breaks so it doesn't even need the feature.