Probably good for starting new projects. The ecosystem looks clean with separation of concerns. Not worth the pain migrating old projects to Angular 2/3/4/5/6/n, unless you have the resources to do so.
Version 6 of Angular Now Available
21–30 of 86 posts
Re: Version 6 of Angular Now Available
#22Was 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.
Same, they handled the transition terribly, I really wanted to use angular but I stuck with knockout and then ended up going to VueJs instead.
Re: Version 6 of Angular Now Available
#23What 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…
I'm not sure what you mean by "churn for churn's sake"?
The AngularJS to Angular upgrade step is a big one. But, the latter is unquestionably a better framework once you're using it. It only needs to be done once, and it can be done gradually, if you're willing to ship both frameworks for a while. The upgrade modules they provide for running AngularJS code in Angular (and vice-versa) were a bit dodgy at first, but they are excellent now.
Once you're on Angular, there's no need for any 6-month rewrites. We upgraded about a year and a half ago, and we've kept up to date without facing any problems with backwards incompatible changes or upgrade pain. The Angular team has done a lot of work on improving the framework's internals, but the actual conceptual model and interfaces have remained stable.
Plus, if you use Angular CLI, you're also isolated from churn in the build tool world. You don't have to worry about juggling compatible versions of Webpack and its myriad loaders and plugins. It's all hidden away. Having wasted far too many hours of my life hacking on Grunt, then Gulp, then Webpack configs, that's reason enough to use Angular for me.
Re: Version 6 of Angular Now Available
#24What 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 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?
Re: Version 6 of Angular Now Available
#25What 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…
well actually my company has a mixed Angular+AngularJS application.
AngularJS really sucks compared to Angular. Angular is a extremely polished framework. However the size is a problem..
Currently upgrading from 5 to 6 was simple. We didn't need to upgrade 'angular' code. (we just used https://update.angular.io/) basically took me two hours (replacing all rxjs code) (code base is 35k lines of typescript and 14k lohtml)
The biggest pain between 5 and 6 is basically rxjs not angular per se and for that there is rxjs-compat. However the only problem with angular would've been if people would've used the old Http Client, however we started with 4 and directly used 'HttpClient' which also is way better since you can easily have interceptors around it.
Re: Version 6 of Angular Now Available
#26Was 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 libraries, meta-frameworks, techniques and practices that are decidedly less beautiful. After a while, I really found myself missing features from Angular, and struggling to replicate them by wiring together a hodge-podge React++ framework. Instead of being productive, I was wasting an inordinate amount of time trying to discover what the current micro-framework de-jour was for handling a particular problem in React.
For example, Angular supports view encapsulation. So you can write CSS targeting a component, and the framework will ensure that the style rules you write apply only to the HTML rendered by that components, without leaking to other parts of the app. This really is a godsend for properly isolating components in a reusable way. With React, there's a myriad of libraries for doing CSS, but most seem to be abandoned, and none seem to offer as straightforward or as easy style encapsulation as what Angular provides out of the box.
It was a similar story with forms. Which are a rich, reactive API in Angular, but seem to be an afterthought in React. And with dependency injection, both of singleton services and components elsewhere in the hierarchy.
I expect if you go all in on Redux, you can eventually build up a reasonable facsimile of what Angular provides. But from a standing start I think Angular is a much more productive framework, just because it's actually trying to be a framework, whereas React seems to be stuck somewhere between being a UI library and a framework, leaving the community to somewhat badly fill in the gaps.
Re: Version 6 of Angular Now Available
#27Was 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.
We started with Angular.js (1) and then migrated all our projects to 2+ as soon as it left beta. At this point we also evaluated react and later took a look at vue.
The main reason why we stick with Angular are the baked-in best practices and the tooling (angular-cli). Especially if you work on larger projects and have several people working on them, (opinionated) Angular simply makes your life a lot easier. With react (and vue) you have to make so many small decisions when setting up your project, that especially less experienced developers are tempted to make potentially "bad" design decisions (e.g. testing framework, bundling, routing, state management, ... you name it).
Re: Version 6 of Angular Now Available
#28Was 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.
We started with Angular.js (1) and then migrated all our projects to 2+ as soon as it left beta. At this point we also evaluated react and later took a look at vue. The main reason why we stick with Angular are the baked-in best practices and the tooling (angular-cli). Especially if you work on larger projects and have several people working on them, (opinionated) Angular simply makes your life a lot easier. With rea…
At this point in React's lifecycle, there are one or two top choices for each category you mention (ie MobX vs Redux, Jest vs Jasmine, etc) for folks worried about making "bad choices" well I would ask, what makes a choice bad? Is it that a particular state management library is a bad fit for your application? In that case, where it's possible that a library is a bad fit, then how can it be that a one-size-fits-all framework is going to not equally have potential to be a "bad" choice, except with a lot more buy in and difficulty to change down the road?
Re: Version 6 of Angular Now Available
#29Earlier 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?
"rewrite your app in the newest version" is more commonly known as upgrading... 18 months support seems fairly reasonable depending on how breaking new releases are.
Re: Version 6 of Angular Now Available
#30Was 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…
React's functional components and JSX abstraction lend to it's ability to render to any target, which is powerful in and of itself. Furthermore since they are all-in-one functions or classes, they are composible and flexible in a way that Angular components are not. The component is the core of a complex UI program. Worth the up front cost of researching the top one or two solutions for forms or CSS management, and gaining all the benefits of the massive React ecosystem, in my opinion, as well as having the flexibility to evolve more easily when things change (as they always do), than buy all in on a framework. Especially for long lived applications, flexibility and adaptiveness is paramount.