Why AngularJS seems to have Deep Learning Curve for Server-Side Developers?
- Err…AngularJS is a Dependency Injection based framework?: This presents problem right in the start when the server-side developers start with AngularJS. Some of the questions they struggle to find answer in their mind and elsewhere on webpages are following:
- Okay, how does DI happen? Is it using some configuration file that developers has to write separately or is it done using some sort of annotations?
Why AngularJS seems to have Steep Learning Curve for UI Developers?
- What the hell is this dependency injection? Why do I need it? Again, I am getting my work done with jQuery and some functional programming. Why do I need to care about DI which I have known as a object lifecycle management related framework for my server-side developer friends.
- My goodness, now you are pushing MVC in its totality on me when I am comfortable taking care of “View” part in my existing world and server-side developers worry about Controller (C) and Model (M).
- And, why new directives when I am OK with existing HTML directives & jQuery (thankfully). Why do I need to worry about custom directives provided by Angular and the ones that I could as well write. huh!
- Is jQuery not enough for all that I need? Then, Why learn AngularJS?
- 10 reasons why developers should learn AngularJS
- 10 reasons why one should consider adopting AngularJS
- Given you are very familiar with jQuery, why Angular?
- What is AngularJS?