I am learning angular. As a beginner, I feel there is too much fiddling with this thing :-( ...anyway, I guess when you are used to it and understand why everything is the way it is it becomes normal and understandable.

You can apply your rant to almost anything in life :). You have to be very careful when choosing your tools, if you are working on a small site then angular would be overkill. The 'fiddly' aspects at *super* useful at scale. I have a project where I generate multiple frontends using the same [shared] codebase. I have not been able to find another framework that gives me this much flexibility and I have tried a few.

@ymas "You can apply your rant to almost anything in life.." lol, quite true :-)

I guess it all boils down to understanding the entire platform. I just felt I was doing too much and that was just setting it up.

@Banele as you projects grow in size, you will start seeing the usefulness of all the legwork. I am in the camp of keep your architecture as simple as possible so if the setup seems like "too much" then I would suggest trying other frameworks too.

@ymas I'll give it a chance. It was just an impression I had as it's my first time. But, on a grand scheme of things, it's a wonderful and powerful platform.

Lemme know if you need help. Btw I use Angular Material 2 for UI. Recently started a project using Angular + Polymer. Hopefully it goes well.

@ymas which method do you use to deploy different clients? We use a JavaScript prefix to change out different versions of components.

@devrocket hello there! I use the angular cli multi app feature, https://github.com/angular/...

I have one shared module that has all the components that all applications need.

I use component inheritance to customise a component for every different app. My inheritance tree is shallow.

Each app definition does indeed have a different prefix, if this is what you are referring to then we're pretty much using the same mechanism :)

I'm learning Angular as well!

Skip the configuration part by doing everything through angular-cli.

What I'd like to complain about is the docs (again!). Just like AngularJS they are... pretty difficult to parse.

Take the tutorial for example: it covers a lot of ground but because it's written as a story it's super difficult to parse quickly. Important stuff like Subjects is buried deep in one of the chapters and is not covered at all in any other parts of the documentation.

Luckily it's a popular framework so Googling results in useful explanations and blog posts.

Good luck!

Tip from a fellow Angular noobie: read http://reactivex.io/rxjs/manual/... instead of Angular's discussion about Observables.

The ReactiveX docs are much easier to follow and understand. I don't understand why the Angular team decided it is a good idea to describe how to create a custom multicast Observable when there's Subject...