Is learning AngularJS necessary before learning Angular 4-6? [closed] - angularjs

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

Related

How should I learn Ext JS 4.2? [closed]

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 1 year ago.
Improve this question
I've been assigned to a legacy project which runs on Ext JS 4.2. I know JavaScript but I'm totally unaware of Ext JS and I'm having trouble in understanding it. Can someone please guide me on how to learn Ext JS, what approach should be followed and the important topics to be covered? Or what sequence should be followed?
I have been using ExtJS (7.2.0) in a corporate project for six months, these are some tips I would have needed some time ago.
You should start from the official docs and examples given by Sencha:
guide --> the main topics are The Class Systems, MVC Application Architecture and Components, which are the basis of ExtJS;
examples --> I find the KitchenSink example very useful, since you can briefly overview all the components available in the system - you can also give a look to MVC examples, in order to see more complex architectures;
forum --> you can also check out the Sencha forum, which has many interesting topics (many more that you can find here on Stack Overflow).
Since you are using an older version of ExtJS, you will find many materials on the internet, because it was widely used several years ago, while now it is difficult to find updated sources.
You can check out Saki website or fiddle explorer sorting by created date ASC:
I used to be a trainer for Sencha, and I left the company in 2013 right around the time when ExtJS 4.2 was the main version.
The fastest way to get up to speed on the framework is to take a training class from Sencha. I haven't worked for Sencha for 8 years, and many of my colleagues (who I respected highly as trainers) aren't there any more, so this is not a plug for their services, but it's the fastest way. You will learn shortcuts that will take you much longer if you were to do it yourself. The framework is huge an complicated, and it's nice to get an overview of how it works from an experienced guide.
Before I was hired as a trainer, I took both the ExtJS and Sencha Touch classes that they had available, and the difference between the "before" and "after" in my understanding was huge. Yes, it's a week of your time, and yes, it's $2500, so your manager may not agree with my recommendation, but like I said, it's the fastest way to get up to speed.
If you do decide to take the class, spend some time with your legacy app and write down where you're getting stuck, and ask those questions in class. Part of the class value is that you can get some free light consulting for any issues you may be having.
The fact that you know Javascript is a big plus. I've had people in my classes who were new to Javascript, and that was another hurdle that they had to get over.
Good luck with your app!

Has angular been replaced with typescript? [closed]

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
So I went through a good tutorial of Angular 1.x.
I visited angular.io to have a look at Angular 2.
All I can see is Typescript, Javascript, and Dart references.
Is what I learnt about Angular pointless now and should I start learning Typescript?
Thanks
TypeScript is only a superset of Javascript. So everything you can do in JS, you can automatically do with TypeScript, too.
With Angular 2 the whole framework changed. Things that partially stayed similar is the template rendering, where only a few keywords changed their name, but the overall concept stayed the same.
The approach for building the app however changed completely.
I'd suggest this article. Be careful though, since a few things stated on that page are already outdated again.
Yes, of course you should start learning Angular2 with Typescript(or any other available platform).
Angular2 framework has been written from the scratch in Typescript.
Believe me by far its one of the best frameworks available nowadays.It provides many features(You'll come to know once you start learning it). Testing components has become so easy.
You can use javascript, dart & typescript with Angular2. I prefer to use Typescript with Angular2. Compare to Javascript, typescript is easy and helpful. There is a separate process which converts your typescript code to javascript code.
while coming from Angular1.x(with JS) background, I understand it is not easy as Angular2.0 is not directly related to Angular1.x.
But soon Angular1.x will be replaced by Angular2.0 and then you will have to learn it so better to start learning now.
Additionally, you can migrate your Angular1.x apps to Angular2.0 with upgrade process
I have so many things to say but I think this much will help to go ahead.

Angular 1 or Angular 2 going forward [closed]

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.

Why should I use Angular 2? What are it's advantages over Angular 1? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Angular 1 excels in data binding and provided a structued MVC MVW framework.
It fails in providing built-in modularity.
What are the core selling points of Angular 2? Im not looking for opinion, just plain simple bullet point facts and Im only interested in core selling points.
Also what other libraries such as bootstrap / polymer gel well with angular 2?
For me? Just off the top of my head:
Support for Functional Reactive Programming using RxJS Observables.
Built from the ground up with Typescript, meaning Types are a first class construct.
Unidirectional data flow.
Native ES6 Modules, no more endless script tags.
Fully component based.
Better template syntax.
An even better Router.
Much better Dependency Injection.
Support for sped up initial loads thanks to server-side prerendering.
ZoneJS Support, no more digest loop!
Of those my favorite feature is definitely the FRP support. We can drastically enhance performance by using Immutable Objects or Observables for our change detection.
The Formbuilder API as well as the HTTP API is fully compatible with RxJS making it very very powerful.
As for libraries, Angular-Material is obviously a big one. Another favorite of mine is NativeScript, which aims to create fully native mobile applications from your Angular 2 App. I'm sure there'll be tons more once it actually releases.

Will Angular 1 die after the release of Angular 2.0? [closed]

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.

Resources