How do you think of angularjs application

AngularJS was revolutionary when it first came out, but if you want to be in the Angularverse, I would strongly encourage you to continue with the latest Angular versions. AngularJS is deprecated, which means eventually you will have to replace it, so you will be doing youself no favors in the long-term by starting new projects in AngularJS.

If you are considering AngularJS over Angular 2+ because you prefer its syntax, you should check out VueJS instead. It looks and works a lot like AngularJS, but is actively maintained, and quite frankly feels a lot less magical and more tangible, more like you can actually understand what it's doing. Not only that, but Vue has a great community around it, and it's currently the most highly-starred project on Github, even beating React.

Many people underestimate the longevity of web applications. The lifecycle in enterprise projects is different, and longer than well, than that of your average marketing campain web site / landing page.

Companies are protective of their investments (rightfully so) - and there is just no way, that an application is rewritten, just because a new framework is released. I really don't want to know how many GWT apps are still alive and kicking (kicking their developers' asses, that is. Anybody who had to debug such a thing might know what I mean... ;))

And Angular and AngularJS 1.x simply are two different frameworks. The fact that they share the brand name and Google as the corporate sponsor, and the people working on Angular who have been formerly AngularJS developers should not fool anybody. Not even the utilities that have been provided to help ease migrations, can hide the fact that every migration of an AngularJS app to an Angular app is a rewrite.

There aren't very many arguments for choosing AngularJS for a new project (half a decade ago, that was different). The rare exception might be the combination of a short lived project and a developer is already very familiar with it, maybe. But then I agree with @cjbrooks12 - Vue would be the more plausible choice.

Actually, for a green field project I'd think most current frameworks are fair game. I've been working with Angular since beta7 (that is somewhat over two-and-a-half years now), and am happy with it. I think the component-based architecture will, with the advent of web components, lead to a better interoperability in the long run, so that need for re-writes will decrease in the future (or less idealistically speaking, they'll at least become cheaper).

does angularjs still exist?

It was cool years ago. the first time i wanted to develop with JS because there was a structure. now its old, the second time you always make a lot of stuff much better then the first time :)

• Very stable and can be optimized to be used for some very large applications.
• It's already a mature environment, so you don't have to re-learn much when updates come your way.
• There are enough libraries for almost any use case, albeit, not all are stable enough.
• The framework is in long term support by the original authors until 2021.

I don't understand why does it still exists, probably because of the legacy projects that are hard to refactor.
Angular 6 launched this year, so 1x is like ancient Egypt in web terms.