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

Version 6 of Angular Now Available

blog.angular.io

Post reply on HN
Print view View original

31–40 of 86 posts

Re: Version 6 of Angular Now Available

#31

Post by Kamshak »

rantanplan wrote: post #24
kromem wrote: post #18

Earlier quoted context omitted.

Angular 6 and all future main releases will be supported for 18 months. As for backwards compatibility, as was described in the presentation on the new renderer they are working on, 600 apps at Google are built on Angular, so there is a great deal of internal pressure to make sure backwards compatibility is a constant consideration. Along those lines, one of the big tooling features in this release is the upgrade com…

> Angular 6 and all future main releases will be supported for 18 months. Does that mean that every 18 months you'd have to rewrite your app in the newer angular version? And if not, what does it mean?

They provide automatic upgrades that work on ASTs so lot's of upgrade refactoring is done automatically

Re: Version 6 of Angular Now Available

#32

Post by jontro »

stupidcar wrote: post #26
antonkm wrote: post #13

Was a firm believer in Angular when it was version 2, made the switch to React before Angular version 4. Best choice I've done for productivity.

I'd offer the opposite perspective: I started a recent app in React, and I wish I'd stuck with Angular. The core of the React render model is beautiful. It's far quicker to start writing and using a new component in React than in Angular, and the functional nature of React components feels good and highly productive. At first. But the problem is, around that beautiful core, the React community has built a mass of lib…

For view encapsulation I really recommend using https://github.com/styled-components/styled-components We use this in all our react projects and we haven't had any problems since with leakage

Re: Version 6 of Angular Now Available

#33

Post by mmargerum »

pbedat wrote: post #14
megaman22 wrote: post #8

What is the backwards compatibility and support model for Angular? I just don't have time to chase after things that move this quickly, not and fulfill all my other responsibilities. I'm supporting a mature application that has a front-end started less than eighteen months ago with AngularJS. Maintenance and support on third-party components we use is already starting to dry up. Rewriting things every six months is n…

We recently began migrating a 4 year old and constantly growing angularjs 1.4 app to react. With angular2react and ngreact we don't face a lot of hard decisions, because we may use angular comps in react and vice versa. We have bootstrapped a angular 4/5 app at the same time, but react just feels right.

Vue feels much more like the natural successor to angular 1 than angular 6 or react are. The least ceremony to getting sh## done framework. React is just a view layer. You are going to have to pull in libraries for routing and state management (at least)

I spent 3 months evaluating all 3 with a poc app and vue was the clear winner for me

Re: Version 6 of Angular Now Available

#34

Post by smuemd »

stupidcar wrote: post #26
antonkm wrote: post #13

Was a firm believer in Angular when it was version 2, made the switch to React before Angular version 4. Best choice I've done for productivity.

I'd offer the opposite perspective: I started a recent app in React, and I wish I'd stuck with Angular. The core of the React render model is beautiful. It's far quicker to start writing and using a new component in React than in Angular, and the functional nature of React components feels good and highly productive. At first. But the problem is, around that beautiful core, the React community has built a mass of lib…

Check out this pattern http://meiosis.js.org

Works great along w react

Re: Version 6 of Angular Now Available

#36

Post by PunchTornado »

smuemd wrote: post #34
stupidcar wrote: post #26

Earlier quoted context omitted.

I'd offer the opposite perspective: I started a recent app in React, and I wish I'd stuck with Angular. The core of the React render model is beautiful. It's far quicker to start writing and using a new component in React than in Angular, and the functional nature of React components feels good and highly productive. At first. But the problem is, around that beautiful core, the React community has built a mass of lib…

Check out this pattern http://meiosis.js.org Works great along w react

your comment proves his point exactly.

Re: Version 6 of Angular Now Available

#37

Post by bob1029 »

Sigh.

Yet more confirmation that my team has made the correct choice in switching to a mostly vanilla JS development stack (we still use RiotJS for one-way template binding). I was there for the beginning of Angular and it got me hooked on single page applications, but what I am seeing now is the antithesis of productivity.

No one building a website for a business should be using this stuff, unless they drank so much frontend framework kool-aid that they cant find their car keys without an NPM command anymore. I don't care how many internal projects at google use this framework. Our business doesn't have billions of dollars to incinerate on attempts to prove a point.

The means of successfully executing SPA and managing your UX state are not intrinsically linked with using someone's subjective interpretation of how it should go (aka a frontend framework). Treat the browser and the DOM like an actual canvas and stop looking through the perspectives of others to see it. Focus on what you want to build, not the tools you use to build it. The fact that there are literally hundreds of angular-style frontend frameworks with wildly different approaches should be a warning sign to developers looking for a consistent basis upon which to build shit.

Re: Version 6 of Angular Now Available

#38

Post by megaman22 »

davidjnelson wrote: post #12
megaman22 wrote: post #8

What is the backwards compatibility and support model for Angular? I just don't have time to chase after things that move this quickly, not and fulfill all my other responsibilities. I'm supporting a mature application that has a front-end started less than eighteen months ago with AngularJS. Maintenance and support on third-party components we use is already starting to dry up. Rewriting things every six months is n…

Angular 2 came out in 2016. Why use angular 1 in 2017?

It was 2016 when we started this front-end rewrite, away from a mess of jQuery and Razor view spaghetti. Angular 2 was brand new, without much support for third-party components we used, and AngularJS looked like the mature option. Probably should have bet the other horse, but c'est la vie.

Re: Version 6 of Angular Now Available

#39

Post by alceta »

I was joyfully expecting this upgrade and checked the release notes daily during the RC phase. Don't let the quick 'major' version changes shock you, upgrading 4 -> 5 was easy and I expect the same for this upgrade.

A big thanks to everyone involved in shaping this release and ensuring the upgradability for the past major versions, including the huge effort in making it possible to continuously migrate from AngularJS. If you care for the details behind my experiences:

We have begun migrating a ~80k loc AngularJS codebase first to TypeScript in 2016, which was the preparation for the Angular upgrade starting Q1 this year. Now we are roughly 80% migrated to Angular 5 (in the meantime we did the upgrade from 4 to 5 in a few hours thanks to https://update.angular.io/), the rest running with ui-router hybrid [1] and ngUpgrade [2] and now are looking forward to moving the rest to Angular and upgrading to 6.0.

Coming from AngularJS where many things are done without a proper reason, I have started to embrace and even somewhat love Angular for the niceties it brings it. When you already embraced TypeScript, it is a breeze to work with and I cannot recommend it enough (for large-scale frontends this is).

The one pitfall I always ended up with during the migration was that AngularJS attribute directives cannot be converted to Angular and then downgraded (In the hybrid app, the entry component is always(?) AngularJS and up from there), which is a large part of the remaining AngularJS code. There are a few workarounds but they did not seem to work properly. If anyone has suggestions on that part.

[1] https://github.com/ui-router/angular-hybrid [2] https://angular.io/guide/upgrade

Re: Version 6 of Angular Now Available

#40

Post by dbbk »

alceta wrote: post #39

I was joyfully expecting this upgrade and checked the release notes daily during the RC phase. Don't let the quick 'major' version changes shock you, upgrading 4 -> 5 was easy and I expect the same for this upgrade. A big thanks to everyone involved in shaping this release and ensuring the upgradability for the past major versions, including the huge effort in making it possible to continuously migrate from AngularJS…

Out of interest, have you looked into EmberJS? That has by far the smoothest upgrade process I've come across. One CLI command upgrades your dependencies, does a diff against a new greenfield project and applies the changes to your application, and also runs any codemods to migrate your code to a new pattern.
Post reply on HN