Learning Angular is ridiculously difficult. Not because Angular is difficult, but because you need to teach yourself a gazillion unrelated technologies before you can create a real Angular application

Creating a “real” Angular app is ridiculously difficult, because it requires you to learn some sort of backend technology, SQL, HTTP and a gazillion other unrelated technologies. This implies that before you can create as much as a single (useful) Hello World app in Angular, you’ve spent the larger parts of a decade to learn unrelated technologies required to know before you can connect your Angular app to a database, and actually do something useful with your app. If you want a .Net backend for instance, you’ll need to know the following.

• C#
• .Net class hierarchy
• Basic OOP
• Basic design pattern theory
• SQL if you’re using an SQL database
• Some database theory
• HTTP
• Etc, etc, etc

Simply the number of classes in .Net you’ll need to study, understand, and consume, rapidly becomes mind blowing. This is before you even start out with the Angular parts of your app. Sure you could create a pure Angular application, and simply ignore the server altogether - But if you do, your app is little more than fancy animations and beautifully constructed buttons, coupled inside animating navbars and tabs. If you want to create a “real” Angular app though, you’ll need some sort of backend, which of course implies spending 85% of your time, on things not even remotely related to Angular in any ways what so ever. Having a real backend as you learn Angular, is also for obvious reasons a million times funnier as you start out learning.

#angular