[mgkimsal]

... because jobs?

I'm in agreement with your point, but... if 'the market' wants angular... 'the market' is going to have a hell of a time dealing with a mess in a couple of years when many of the decision makers that mandated angular move on to something else and leave piles of mess behind for someone else to clean up.

[emilis_info]

There may not be moving on. Or it may take a very long time. Angular is that big already.

Previously there was no the framework for web frontend development (like Rails for Ruby). From now on you will need convincing reasons to use anything else, even if it is clearly better. Moving on to something else will be much harder.

[rimantas]

Is it big in production deployments or only in hiring managers wishes?

[emilis_info]

I would like to know an answer to that question.

On the other hand my wish is not to get into stupid arguments at my new job :)

[Bahamut]

I don't think that problem is restricted to Angular - it's one that you see with when developers wrote unmodular code period. I saw it with legacy ExtJS code.

[mgkimsal]

Oh I completely agree it's not an angular thing. It was a Rails thing, is or will be a 'node' thing, etc. It will be a docker thing at some point too. There's a rush to 'new' that appears to everyone to be 'it', people use 'it' for a bit, realize it doesn't solve all problems, then move on to something else. They've done a lot of learning on someone's dime, moved on, but left a mess of code for someone else to 'maintain' for years. The cycle will continue to repeat itself for a long time...

[jacquesm]

> when many of the decision makers that mandated angular move on to something else and leave piles of mess behind for someone else to clean up.

That's already happening. Two contacts came up in the last two weeks with Angular projects gone off the rails (pun intended).