Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 5.0.0

blog.angular.io

Post reply on HN
Print view View original

61–70 of 189 posts

Re: Angular 5.0.0

#61

Post by fknop »

usrusr wrote: post #48
evmar wrote: post #18

Earlier quoted context omitted.

They are following semver: http://semver.org/ So the major version changes whenever they make a backwards-incompatible change. However, I clicked in their upgrade calculator (linked from the post) and at a glance it appears the incompatible changes are fairly minor.

But did semver really set out to eradicate all distinction between minor incompatibilities and complete architectural reboots? So much semver adoption seems to be based entirely on wishful thinking. Step 1: hey, perfect drop-in compatibility would be so cool Step 2: we can do it, with semver! Step 3: we use semver! Yay us! Step 4: oh, turns out adopting semver did not make perfect drop in compatibility any easier Ste…

They do actually use every number of semver in a meaninful way.

Re: Angular 5.0.0

#62

Post by tptacek »

kevan wrote: post #53
tptacek wrote: post #36

Earlier quoted context omitted.

People say this a lot. But the React you write in 2017 is pretty close to the React you'd have written the year the framework was released.

Most of my pain with the React ecosystem happened when people kept rebuilding react-router every 6 months. I managed one upgrade, but after that we gave up and stuck with the old version because it worked well for our purposes.

Certainly, the React ecosystem is full of stuff that changes gratuitously --- but my feeling is the rate of change on that stuff is usually inversely proportional to its utility. For instance: I'm not entirely sure why anyone uses an add-on router library.

Re: Angular 5.0.0

#63

Post by fknop »

merb wrote: post #50

`ng serve --aot` will be default? thanks... please fix: https://github.com/angular/angular-cli/issues/6742 before..

You can still use --no-aot (or something similar) in the meantime

Re: Angular 5.0.0

#64

Post by ptmcc »

maxpert wrote: post #47

Have recently moved system from TS + Angular 1 to Angular 1.5 and then to Angular 2 (took us solid 1 year and you can still see some traces of older code), by time we finished move to 2, Angular 4 was released! And now this! This is WTF moment of my life.

There's very few incompatibilities from the 2.0 release onward.

A few minor things here and there, and a few deprecations, but by and large most everything that worked in 2.0 should still work in 5.0.

Re: Angular 5.0.0

#66

Post by dragonwriter »

usrusr wrote: post #48
evmar wrote: post #18

Earlier quoted context omitted.

They are following semver: http://semver.org/ So the major version changes whenever they make a backwards-incompatible change. However, I clicked in their upgrade calculator (linked from the post) and at a glance it appears the incompatible changes are fairly minor.

But did semver really set out to eradicate all distinction between minor incompatibilities and complete architectural reboots? So much semver adoption seems to be based entirely on wishful thinking. Step 1: hey, perfect drop-in compatibility would be so cool Step 2: we can do it, with semver! Step 3: we use semver! Yay us! Step 4: oh, turns out adopting semver did not make perfect drop in compatibility any easier Ste…

> But did semver really set out to eradicate all distinction between minor incompatibilities and complete architectural reboots?

It's explicit terms do, whether or not that's the intent. Backward incompatible is a bright line.

OTOH, I think that exact bright line is the central purpose of SemVer.

Re: Angular 5.0.0

#67

Post by perseusprime11 »

Yabood wrote: post #14

This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.

I hear you. What's causing them to iterate so fast? I still remember the days of Java and .Net where they did yearly releases and phased transitions with good documentation of what's deprecated and what's new.

Re: Angular 5.0.0

#68

Post by fknop »

merb wrote: post #50

`ng serve --aot` will be default? thanks... please fix: https://github.com/angular/angular-cli/issues/6742 before..

They actually reverted aot by default on serve because for really large project it might slow down the reload time.

Re: Angular 5.0.0

#69

Post by pbowyer »

perseusprime11 wrote: post #67
Yabood wrote: post #14

This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.

I hear you. What's causing them to iterate so fast? I still remember the days of Java and .Net where they did yearly releases and phased transitions with good documentation of what's deprecated and what's new.

> and phased transitions with good documentation of what's deprecated and what's new.

If you're after that >> https://emberjs.com

Re: Angular 5.0.0

#70

Post by adventurer »

pythonaut_16 wrote: post #26
Yabood wrote: post #14

This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.

Vue.js can be a good option for shops coming from Angular 1.x.

When Angular 1 was left for dead I went to Knockout. I think it is very similar and also very simple to use.
Post reply on HN