What is AngularJS?
Who uses AngularJS?
Why developers like AngularJS?
Here are some stack decisions, common use cases and reviews by members of with AngularJS in their tech stack.
I use AngularJS because it was back in the days one of the interesting and most hyped frameworks. Especially the two-way databinding and the amount of free angular-components from the community made the development of this research project very easy and fast. React on the other side, was just on the geginning of its rise and Angular promised a more SPA approach, also with HTML & CSS templating, which I had experience from the past. React with JSX was too new for me and a bigger overhead, so I tried AngularJS. Today with no backward support of Angular 2.x/ - /8.x, I personally switched to Vue.js as it shares many concepts from Angular & React and is easy to learn.
The whole frontend and the most analytics functions are hosted directly in the browser based on a RESTful API. AngularJS
Among the best Front-End JS Framework Update: React & Angular2 are now leading but we are now stuck with AngularJS :-) AngularJS
Here are some stack decisions, common use cases and reviews by companies and developers who chose AngularJS in their tech stack.
When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:
- Many in our community are already using React internally and will be able to contribute.
- Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.
So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.
By switching our state management to MobX we removed approximately 40% of our boilerplate code and simplified our front-end development flow, which in the ends allowed us to focus more into product features rather than architectural choices.
Back in 2015, my company had a back-office dashboard that was originally built in AngularJS 1. Since Angular 2 presented drastic changes we decided to rethink the options and we looked at React and Vue.js. Besides, at the time, Vue had basically only one developer, its structure (100% oriented to components) and also its backward compatibility focus (Angular 1 to 2 no more) we preferred it against React cause it seemed more straightforward, clean and with a small learning curve. Now 4-5 years later we are very happy with our choice.
When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.
The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.
We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.
We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.