Angular 5.1 and More Now Available

Post by chmln » Thu, Dec 07, 2017, 7:24 AM UTC

adpirz wrote: post #6

Can anyone speak to their successes with Angular post 2.0? I feel like any time it comes up, it's mostly horror stories about the transition or how shops have just moved on to Vue, etc. Is it worth still considering / where does Angular shine where React and Vue come up short?

It shines by being extremely opinionated, but imo the tradeoffs are not worth it.

I was initially very curious about Angular2, but our relationship ended very quickly with the discovery of modules and dependency injection. It feels like some kind of arcane over-engineering compared to React's (and vue's) simple and sufficient import-and-use model.

Post by ProblemFactory » Thu, Dec 07, 2017, 1:27 PM UTC

at-fates-hands wrote: post #33

ProblemFactory wrote: post #12

Earlier quoted context omitted.

4 -> 5 included some new cool features but was a smooth upgrade. 6 is coming out in March and then a new "major version" is scheduled every 6 months. This is common for end-user apps but feels very weird for developer libraries and frameworks. We are used to X.Y.Z releases where X are "major rewrite", Y are significant updates, and Z are bugfixes. That said, Angular's new scheme could be technically correct strict "s…

> 6 is coming out in March and then a new "major version" is scheduled every 6 months. I work in a large corporation and they're still planning their transition to 1.5 and then to 2. I'm keeping up by building stuff in my off time, but trying to keep a fortune 200 corporation on a six month upgrade track? Not happening. I've already heard rumblings from upper management of going back to some open source Java framewor…

> I work in a large corporation and they're still planning their transition to 1.5 and then to 2.

Angular 1 -> 2 is an actual "major release". "Rewrite all your apps from scratch" major.

But starting from Angular 4, the "major version number changes" doesn't mean a major effort to update. There's a decent chance that 4 -> 5 -> 6 -> 7 etc will work without any code changes. But as long as there is a backwards-incompatible change, no matter how small and in how obscure submodule, it requires bumping the version number according to semver.

Most enterprise users will probably skip multiple versions between upgrades, just as they skip Ubuntu releases and Django releases and Rails releases and so on.

Re: Angular 5.1 and More Now Available

Re: Angular 5.1 and More Now Available