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

Angular 5.1 and More Now Available

blog.angular.io

Post reply on HN
Print view View original

11–20 of 42 posts

Re: Angular 5.1 and More Now Available

#11

Post by pritambarhate »

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?

We are working on 4-5 large admin apps (60-80 screens) using Angular and PrimeNG. After initial training the team (8-10 programmers) was very productive. The bundle size is a little large. But it has improved a lot with Angular 5.

Quite happy so far.

Re: Angular 5.1 and More Now Available

#12

Post by ProblemFactory »

pcurve wrote: post #7

I thought this was some kind of joke... until I realized they skipped v3. But still, v5 already? Or did I just get used to Bootstrap 4 being in Alpha for years?

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 "semantic versioning". In semver X.Y.Z, Z releases are supposed to be bugfixes with no feature additions, Y releases add features but with perfect backwards compatibility, and X releases introduce breaking changes. A backwards incompatible change, no matter how small and easy to adjust for, should be a major version bump according to semver.

Re: Angular 5.1 and More Now Available

#13

Post by jrs95 »

ChristianBundy wrote: post #10
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?

Angular is _fine_, but it's largely a "me too" framework that brings nothing new to the table. On the other hand, it insists on using a non-standard language, which breaks all of the tooling used in the rest of the JS ecosystem. React and Vue are reasonable options, but as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.

I understand the Angular part but why Typescript?

Re: Angular 5.1 and More Now Available

#14

Post by pluma »

pcurve wrote: post #7

I thought this was some kind of joke... until I realized they skipped v3. But still, v5 already? Or did I just get used to Bootstrap 4 being in Alpha for years?

Still playing catch-up. React is already on 16.

Joking aside, apart from semver another reason for the weird versioning in Angular is that it's a rather large collection of modules, especially if you include things like RxJS (which technically aren't exclusively part of Angular but affect APIs due to their widespread use). So it's fairly easy to get a semver major version bump because of an implementation detail you likely wouldn't care about but that breaks backwards compatibility with some older library in some way.

Re: Angular 5.1 and More Now Available

#15

Post by shusson »

ChristianBundy wrote: post #10
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?

Angular is _fine_, but it's largely a "me too" framework that brings nothing new to the table. On the other hand, it insists on using a non-standard language, which breaks all of the tooling used in the rest of the JS ecosystem. React and Vue are reasonable options, but as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.

> as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript

Say what you will about Angular, but why the hate on TypeScript? I've found using TypeScript one of the better experiences I've had in the Angular ecosystem.

Re: Angular 5.1 and More Now Available

#16

Post by connor4312 »

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?

We use it on an app that's a bit over 100k lines of our own code. It works fine, there are some gotchas but overall it's as decent to work with as any other framework. Build setup is a bit of a bear but that is largely due to our own requirements and patterns.

Re: Angular 5.1 and More Now Available

#17

Post by pluma »

ProblemFactory wrote: post #12
pcurve wrote: post #7

I thought this was some kind of joke... until I realized they skipped v3. But still, v5 already? Or did I just get used to Bootstrap 4 being in Alpha for years?

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…

It'd be interesting to see Angular join the React bandwagon and embrace codemods. React has broken compatibility several times (though you now get deprecation warnings on the final minor release before a breaking major) but Facebook has an internal policy that if React breaks compatibility, the React team has to fix the application code it breaks -- which has lead to every breaking change coming with codemods which can automate the necessary adjustments, making upgrades significantly smoother.

Re: Angular 5.1 and More Now Available

#19

Post by pluma »

zitterbewegung wrote: post #4
candiodari wrote: post #3

I'm still on 1.0. Not changing either.

Which 1.0 are you using? I'm on 1.6

Not OP but I'm still on 1.2 because I still had to support IE8 when 1.3 dropped it out of the blue (I wouldn't have used 1.2 if I had known the Angular team planned to drop IE8 support). Shortly after, Angular 2.0 was announced and at the point where IE8 was no longer a requirement Angular 2.0 was still not stable but not far away enough to justify spending energy upgrading the codebase to another 1.x release in the meantime (especially as AtScript was still a thing and there was no clear upgrade path yet).

The app is still in production but parts of it have been rewritten in React since. Despite the added weight of another library, introducing React ironically helped reduce the file size (mostly because it allowed us to remove dependencies that were no longer necessary and the build process changed with bower being replaced by yarn).

EDIT: Another factor in the decision not to upgrade to 1.x when we were able to drop IE8 support as a requirement was that the removal of IE8 support came so abruptly that we decided not to trust Angular to support any browsers that aren't on the latest version (i.e. we expected them to drop IE9 support equally sudden and it seemed clear that Angular 2.0 wasn't going to be built with compatibility in mind).

For comparison, when we added React to the project two years later (when IE8 was no longer a requirement), React still supported IE8 and only several months later announced that they would drop support with the next release. But even then "dropping support" meant that bugs were deprioritised whereas the AngularJS announcement heavily suggested that existing code for IE8 would be intentionally removed or rewritten in a way that breaks compatibility outright and the code should be expected not to work in IE8 at all.

So based on how the announcements were made and what "dropping support" entailed in each library, React seemed the safer bet.

Re: Angular 5.1 and More Now Available

#20

Post by kylecordes »

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?

Getting from 1 to 2 was quite an experience. Much discussed here and elsewhere.

Thereafter though, they have been just relentlessly polishing, improving, smoothing rough edges, making bundle smaller, making compilation and execution faster, etc. It is really a model of exactly what you would want, in terms of a joint respect for backward compatibility with forward progress.

I don't understand the "haters" in some peer comments. There are certainly interesting things to consider in terms of feature and approach differences between Angular and its competitors. You could certainly find bits where a simpler approach taken by one of the competitors is a quicker learning curve and smaller size.

But at the same time Angular has a substantial feature footprint, it has significant swaths of functionality that the competitors don't address. We've been using (leveraging like crazy!) the Angular forms system. Many enterprise and non-enterprise applications have lots and lots of forms. Not forms in the trivial sense of, some controls on the screen. Complex interconnected behavior. Angular brings a lot to the table here.

Post reply on HN