Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I don't think this is an easy question to answer but I am unable to find a comparison of the use cases for angular 1 and 2 rather than simply listing the new features. At my work we develop client side only web apps, we are not allowed to use a server, all of our content is loaded and delivered through iPads, and our development team is small and (relatively) inexperienced. We are just wrapping up an angular 1 project and are about to start a new project that is based on this recently finished one, it will be however much larger in scope and functionality. Because of this we thought it might be a good time to transition since we have already figured out the basic logic and structure of how this larger project will work. So I guess the best way to break it down is as follows:
are there any benefits (over angular 1) to angular 2, excluding features that depend on a server?
are there types of applications that angular 2 is better suited for?
does the community at large view angular 1 and 2 as coexisting with both being developed and supported or is it going to be angular 2 going forward?
am I looking at this completely wrong and it's not an all out nothing approach and we can develop in both?
Any advice is appreciated, if this is on the wrong section let me know and I will move it.
I don't think there is any question that you should be moving into Angular 2. Especially now that Angular 2 has reached the stage of Release Candidate. If not migrating from 1 to 2, then starting your new project completely in Angular 2.
Angular 2 is a completely new framework and, in my opinion, much easier and simplified. There are a whole array of reasons why Angular 2 is better than Angular 1, not the least of which is that Angular 2 is much faster and is the future as far as Angular development is concerned.
Yes there are some growing pains, but I firmly believe you will be very happy with Angular 2 and not look back. Take the time to learn it and you will be very happy you did.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I want to pursue towards becoming a FULL stack developer before that I want to get my grip on Angular.
I already know about the differences between AngularJS and Angular, my question is,
Is it necessary to learn AngularJS before learning Angular 4-6?
If not, can I apply for any project/job that has a listing requirement of AngularJS?
Summary: Can I directly learn Angular 4-6 from scratch without AngularJS?
Also, please suggest regarding which version of Angular (2-6) should be choosed to learn from scratch.
no it is not necessary to know AngularJs to lear Angular4-6 but i recommend you to first take a look on typeScript because it is necessary before you get started with Angular4-6 you should start with Angular5 because it is latest and there is not much difference in Angular5 and Angular6 which is better for getting familiar with Angular
You may skip AngularJS, though understanding vanilla, ECMA javascript and typescript is at must before you start to learn any kind of JS framework.
Talking about which version to start learning, I'd rather started upon learning the latest version possible, then invested some time reviewing changelog afterwards.
While you understand that tech, the latest version will become stable and popular.
While they share many concepts, AngularJS and Angular are two completely independent frameworks. There is no need to know one before learning the other.
Angular is very different from AngularJS. Ultimate version of AngularJS has been released so it is in sunset phase of it's life now...
http://www.codelord.net/2018/02/04/angularjs-1-dot-7-the-ultimate-version/
Google say that in October 2017 the number of active Angular (that is,
2+) developers has surpassed that of AngularJS developers, which was
their cue all along to when they can start wrapping up 1.x.
Regarding the job - I think that future of the angularJS projects is migration to Angular/Vue/React so your Angular skills might be relevant. You may apply and let them decide.
I suggest to start learning from the most actual version which is 6 now
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I'm learning angular 1, however, angular 2 is in Beta and can be released soon.
Question.
Start a website with angular 1 and then I upgrade to angular 2?or beginning make angular 2 with typescript?.
I am in doubt what to do, I do not know if I start with angular 1 or already invest in angular 2
on his twitter angular, put a new update on angular 2
Thanks.
The two are completely different. So, it depends on your propose.
If your website cannot has any bugs, you probably should use ng1.
If your site can have some bugs sometimes, you should use ng2.
Why?
Ng1 will have google support until at least 2018, so, dont be afraid that your site wont be up to date.
Ng2 is the future, using modern technologies and the new ECS features. Totaly different from ng1, so almost everything that you lear in ng1 wont be used in developing ng2 apps.
You must think about what you are looking after: knowledgement or a strong and stable tool. Ng1 is strong and stable, Ng2 is the future...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have just started learning Angular 1 and then someone told me that Angular 2.0 has also been released and hence Angular 1 will die. Most of the concept of Angular 1 has been eliminated in Angular 2.0 such as scope etc. This made me kinda confused and hesitated towards learning Angular 1 and also kinda frustrated because I was totally into learning Angular 1. Angular 2.0 is still in its alpha version. What are your suggestions that should I stop learning Angular 1 and focus on Angular 2.0? and is Angular 1 really going to die in the future?
Thanks in anticipation.
Bear in mind that your question is subjective and Stack Overflow is not the most appropriate place ask it.
There are a few reasons why I would suggest sticking with angular 1.* at this stage:
Documentation. There are a vast number of online resources dedicated to learning angular 1.*. This is especially useful if you are new to web development.
Mature tooling support
Mature framework. Common quirks and "gotchas" have already been discovered by other developers, with answers available here on Stack Overflow.
As a compromise, I would suggest learning angular 1.*, but also using it along with Typescript. There is nothing stopping you from dabbling with angular 2.0 while it is in alpha.
Update January 2017
One year on I would definitely recommend that users new to Angular should start learning Angular 2.0 rather than Angular 1.0. I found Angular 2.0 to be much easier to learn and a more pleasant developer experience overall, especially when coupled with angular-cli.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I get it: the API is going to change, possibly in dramatic ways.
However, I make small apps for less than 10 customers each. I'm thinking that I can:
choose a specific version and stick with it
make lots of tests to check for compatibility with new releases
Also, given the projects are small, there's very little code to update when needed.
I realize that the Angular team is communicating the general readiness of their code in terms of availability for adoption from the general developer user-base.
I hear things like:
"Should You Use Angular 2.0 or 1.x?" =>
"The executive summary: There’s no Angular 2 to use, so Angular 1 is still the way to go."
And then I see videos showing how to use it. And I think to myself: with the above strategy of choosing a specific version & sticking with it + doing very careful updates to new releases, I don't see a very compelling reason not to. I mean, the only thing not to do would be not to go complaining to Angular whenever their changes inevitably break my code; it's expected. I'd be disappointed if it didn't break between now & then. That's part of the fun. Fix it and move on.
Concerns:
Security: the only real concern that gives me pause is that some security issue might be in play. But then, that's almost always the case. After all, it is the world of cyber insecurity.
Angular team can still make major changes in syntax and behaviour.
You can just try to use similiar approach with Angular 1.x, especially they introduced .component in Angular 1.5.
So just work with directives and components, after Angular 2.0 release migration should be fairly easy.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
First of all I don't mind the "writing more code" attitude that CI has so I don't really care about that. Right now I'm pretty good in CakePHP (I have like 3-4 years in it) and I think it has certain flaws the biggest one being its speed and I was thinking of passing over to CI but I need to know something..
My simplest application in CakePHP (with admin and some data in table - multilanguage) takes about 0.2 Seconds of code processing. I was wondering if anyone has a time for Code Igniter for a certain website. I'm curious if it's worth the learning time.
I installed code igniter and at first it seemed imensly fast but I'm just worried that if I keep adding components, models, helpers and everything to it it will slow down (maybe more than cake). So.. I'm actually looking for an example of CI website and the exact time it loads... (down to at least 2 decimals).
This thread will give you a fairly good answer, as the site in question is not a "Hello World" but a fully fledged Site with database access helpers and libraries loaded, etc...
I'm sure some will have arguments about its validity (probably CakePHP proponents), but it's not every day you have a site re-developed between frameworks and compared.
UPDATE
Again, for those that don't want to follow the link to the thread, the tester actually upgraded the site to CI 2.0, using modular extentions, caching, other optimizations and re-tested