AngularJS is not a small framework. It has a large surface
area with many new
Concepts to grasp. Its codebase is also substantial, with
35K lines of JavaScript in
It. While all of those new concepts and all of those lines
of code give you powerful
Tools to build the apps you need, they also come with a
learning curve.
I hate working with technologies I don’t quite understand.
Too often, it leads to
Code that just happens to work, not because you truly
understand what it does, but
Because you went through a lot of trial and error to make it
work. Code like that is
Difficult to change and debug. You can’t reason your way
through problems. You
Just poke at the code until it all seems to align.
Frameworks like AngularJS, powerful as they are, are prone
to this kind of code.
Do you understand how Angular does dependency injection? Do
you know the
Mechanics of scope inheritance? What exactly happens during
directive transclusion?
When you don’t know how these things work, as I didn’t when
I started working
with Angular, you just have to go by what the documentation
says. When that isn’t
Enough, you try different things until you have what you
need.
The thing is, while there’s a lot of code in AngularJS, it’s
all just code. It’s no
Different from the code in your applications. Most of it is
well-factored, readable
Code. You can study it to learn how Angular does what it
does. When you’ve done
That, you’re much better equipped to deal with the issues
you face in your daily
Application development work. You’ll know not only what
features Angular provides
To solve a particular problem, but also how those features
work, how to get the most
Out of them, and where they fall short.
No comments:
Post a Comment