Re:Angular 5.2 Now Available – Angular Blog
by stupidcar on Wednesday January 10, 2018 @04:11PM
(#16119102)
We've just upgraded from 4 to 5 and not had any major problems. Most of the issues we encountered were with the stricter type-checking in TypeScript 2.5, not changes to Angular itself. It took me about a morning to do the upgrade.
Overall, using the framework has worked out great. The other front-end frameworks we've used (including ng1) now seem rather toy-like in comparison. The biggest stroke of genius has to the hierarchical dependency injection. Letting a UI component provide injectable services to its children and their descendents instantly solves so much of the tension between integration and reusability that plagued us in the past.
And the template language is also brilliant. It actually understands the difference between binding to the string-based attributes of an HTML element, and the object-based properties of a DOM object.
Re:Angular 5.2 Now Available – Angular Blog
by nicoburns on Wednesday January 10, 2018 @03:50PM
(#16118949)
Its basically pretty comparable to React at this point. You get a few more things out of the box, and its a fair bit harder to debug (but nowhere near as bad as Angular 1.x). Upgrading is painless (and the upgrades themselves are gradually chipping away at pain points in the lib itself)
It lets you diff a simple project generated with different versions of angular-cli; that way you can easily see the any configuration options etc that have changed between releases.
That comment is more or less a recurring experience for me. I've been solving problems that are slightly out-of-the-box of the typical CRUD app, and Angular 2+ has been nothing but pain for me.
Re:Angular 5.2 Now Available – Angular Blog
by dehef on Wednesday January 10, 2018 @04:21PM
(#16119182)
You can transpile with fusebox or ionic cli if angular cli is the problem. For my next project I will use fuseboz with lazy loading (currently I use ionic)
Re:Angular 5.2 Now Available – Angular Blog
by maxxxxx on Wednesday January 10, 2018 @04:22PM
(#16119197)
Is Angular still cool in the JavaScript world? I have to take over an Angular 1 site. We have to make some big changes so we pretty much have to start from scratch no matter what.
Re:Angular 5.2 Now Available – Angular Blog
by eitland on Wednesday January 10, 2018 @05:07PM
(#16119587)
Not cool but well supported and easy to work with.
As other points out if a piece of js is cool today it is outdated somewhere next month.
Having worked extensively with both the old angularjs as well as angular 4 and 5 my recommendation is to switch to the new angular if you are going to keep developing it.
Re:Angular 5.2 Now Available – Angular Blog
by dehef on Wednesday January 10, 2018 @04:30PM
(#16119261)
You own a downgrade + a response :)
Angular doesn't have to be cool to works.
It's a mature framework. I find it very useful and I can do anything with it by now.
Since it's ok with object oriented concept, and still actively backed by google, it will stay attractive in enterprise, most than any other js framework.
Overall, using the framework has worked out great. The other front-end frameworks we've used (including ng1) now seem rather toy-like in comparison. The biggest stroke of genius has to the hierarchical dependency injection. Letting a UI component provide injectable services to its children and their descendents instantly solves so much of the tension between integration and reusability that plagued us in the past.
And the template language is also brilliant. It actually understands the difference between binding to the string-based attributes of an HTML element, and the object-based properties of a DOM object.
Angular is totally ready to be use in prod since a long time now.
Very easy to update:
2-> 4 no gap but my project was starting
4-> 5, very few things on a already big project. In my case the HttpModule, and some internationalization adjustment.
This repo is really useful: https://github.com/cexbrayat/angular-cli-diff
It lets you diff a simple project generated with different versions of angular-cli; that way you can easily see the any configuration options etc that have changed between releases.
That comment is more or less a recurring experience for me. I've been solving problems that are slightly out-of-the-box of the typical CRUD app, and Angular 2+ has been nothing but pain for me.
Specifically, the old model:
request -[latency]> [server] -[latency]> response
Needs to be replaced by:
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
request -[latency]> [server] -[latency]> response
Why ? Because it's faster ! Damn you !
As other points out if a piece of js is cool today it is outdated somewhere next month.
Having worked extensively with both the old angularjs as well as angular 4 and 5 my recommendation is to switch to the new angular if you are going to keep developing it.
This is a major issue.
2+ shouldn't have even used the Angular name IMO.
I've worked with both 1.3-1.5 as well as 2, 4 and 5 and if I inherited a 1.x codebase I'd rewrite it, if necessary one piece at the time.