[IgorPartola]

Phew. After the Angular 2 disaster, I am traumatized by posts with this title format. It seems like the changes will be simple, useful, and mostly backwards compatible. I look forward to upgrading my current Vue projects to use 3.x. I am especially excited about not having to worry about missed observable mutations with arrays. That was annoying.

[jhoh]

How was Angular 2 a disaster? I know it was basically a new Framework but I think they made it very clear and even did a rebranding (AngularJS -> Angular) and AngularJS is still being maintained.

[barbecue_sauce]

While I agree Angular 2 isn't a disaster, AngularJS -> Angular is probably the laziest and most ambiguous "rebranding" I've ever seen, considering the fact that historically AngularJS was often referred to as Angular. This will be a clunky simile, but it's like if all of a sudden Coca-Cola decided to rebrand Cherry Coke as just Coke and branded regular Coke as CokeNC. (Coke NoCherry).

[twblalock]

The front end team at my last company was pretty pissed that they spent months migrating to Angular and then learned that Angular 2 was not backwards compatible.

They were hoping that by going to Angular they were buying in to a platform that would serve them for years, but that was not the case. That’s a huge deal. Why should they trust Angular ever again?

I suspect the Angular 2 debacle was a big factor in moving React ahead of Angular.

[aikah]

> How was Angular 2 a disaster?

Because these were basically 2 different projects that have absolutely nothing in common. They should have called it something else. I'll be hyperbolic but imagine jQuery then jQuery2 is React, to give you an idea. Why still call that jQuery? for marketing purposes obviously and it's a bad reason.

[eksemplar]

Big changes that come so sudden are disasters in the real world where people don’t adopt new things a lightning speed or for free.

If you spend money upgrading your employees from whatever mvc to angular1 and then have to do the same thing a few years later, you’ll be pissed.

If you have to take time out to learn a new framework every two years, just because. You’d be pissed.

And you have to keep in mind that angular was meant for ebpnterprise, not young indies who change their frameworks more often than I change my pants, so that made it extra terrible. I mean, there is a reason COBOL is still a thing, enterprise doesn’t like change.

I guess you could have kept going with angular1, but how would you hire for something that only lived s few years? Nobody knows it.

I think Microsoft is in danger of going this route as well with all the changes they are doing to .net though, so it’s a general trend these days, by my god, it sucks.