Just in case if somebody didn't read to that part, I want to highlight this amazing tool: https://update.angular.io/
Version 6 of Angular Now Available
11–20 of 86 posts
Re: Version 6 of Angular Now Available
#12What 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?
Re: Version 6 of Angular Now Available
#13Was 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.
Re: Version 6 of Angular Now Available
#14What 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.
Re: Version 6 of Angular Now Available
#15What 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?
Legacy project?
Migrating from AngularJS to Angular >= 2.x is not that easy if you build a framework arond AngularJS.
E.g. in my company we use AngularJS because of that.
Re: Version 6 of Angular Now Available
#16Beware that new @angular/cli@6.0.0 doesn't support universal node packages that are using fs/net/stream depending on the environment (e.g. using fs.readFile() when running in Node, while using window.fetch() when running in a browser.) It seems that Angular team made a decision to not have out-of-the-box support for projects using such packages even in the future [1]. [1] https://github.com/angular/angular-cli/issues…
Makes perfect sense to me.
It may sound logical, but unfortunately breaks a lot of existing angular projects and there is no kosher way to configure it to work.
For example both Rust’s stdweb and emscripten are detecting node/browser to load wasm file by appropriate method, they will not work in angular 6 project.
Re: Version 6 of Angular Now Available
#17What 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?
You probably are not aware how many (rather big) projects out there are still on angular 1 with no upgrade plan at all. Last time I turned down a job offer because of a similar scenario.
Re: Version 6 of Angular Now Available
#18What 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 command in the CLI, which can allow packages to self update themselves across your codebase (i.e. if there's a breaking API change, they can rewrite that API call accordingly automatically during package upgrades). This is new, so it's yet to be determined how common and painless the usage will be.
Re: Version 6 of Angular Now Available
#19Earlier quoted context omitted.
Angular 2 came out in 2016. Why use angular 1 in 2017?
You probably are not aware how many (rather big) projects out there are still on angular 1 with no upgrade plan at all. Last time I turned down a job offer because of a similar scenario.
Hi, xab9. Out of interest, why did you turn down a job because they are working with a framework version from 2016?
Re: Version 6 of Angular Now Available
#20Earlier quoted context omitted.
You probably are not aware how many (rather big) projects out there are still on angular 1 with no upgrade plan at all. Last time I turned down a job offer because of a similar scenario.
Hi, xab9. Out of interest, why did you turn down a job because they are working with a framework version from 2016?
This was A1, which came out in 2010. I've spent two years using it, I know its strengths and weaknesses, there are just better offers out there.