Explain like I'm five: AngularJS and when you'd use it.
Andrew Smith
ใป1 min read
Classic DEV Post from Jul 27 '19
210
108
Form errors that help users
Josh Ferrell -
How Knowledge of Information Seeking Behavior Can Enhance your User Interface Design
Stephanie ๐ฎ -
Using jQuery and Bootstrap from a CDN with fallback scripts in ASP.NET Core 3.0
Andrew Lock "Sock" -
Trending on 
I made a free theme ๐จโ๐ป๐ฃ
Using DataLoader to batch API requests
๐ฅ Roadmap Web Developer Front End 2020
Learn Modern React in 2020
Real life comparison of Symfony router and Mezon router
I created my own Pure CSS Micro-Framework, a tale ๐
60fps JS while sorting, mapping and reducing millions of records (with idle-time coroutines)
FRONTEND DEVELOPER GUIDE - PART 2
Sign In With GitHub
Sign In With Twitter
AngularJS is a big piece of JavaScript code that helps you build applications that run on websites. Here's some of what it gives you:
You'd use AngularJS if you joined a team that maintains an old project that was built with AngularJS. You probably wouldn't ever use AngularJS on a brand new project; it has problems with performance and maintainability that can increase as projects grow.
When AngularJS first came out, it was a big deal because it was more ambitious than many other web frameworks and it had the support of Google, which built a lot of hype and excitement around it. But now there are a few frameworks that make more sense to use for new projects, such as Angular (the new version of AngularJS), React, and Vue.
For very small projects, you may not need any framework. But if you're working on a long-lived project with lots of features and several developers, a framework is a good way to keep things standardized so everyone understands what's going on.