I'll begin with quotes from the documentation. "Angular is what HTML would
have been, had it been designed for applications."
"Angular frees you from registering callbacks, manipulating HTML DOM,
programmatically marshalling data to an from the UI, writing tons of
initialization code just to get started."
How's that for encouragement?
Notwithstanding assurances, the documentation is full of geeky jargon with
abstract explanations; without any meaningful context.
https://docs.angularjs.org/guide/introduction
The terminology includes data binding, services, controllers, dependency
injection, templates, directives, expressions, filters, forms, animations,
modules, providers, bootstrap, unit testing, HTML compiler, E2E testing,
etc.
Some of the terms may sound familiar, except in a browser framework they
mostly sound peculiar; like trying to force complex architectural
abstractions into a runtime environment designed for simple UI rendering
and event processing (browsers)
Can't blame it entirely on my personal ineptitude. Angular goals and
concepts are good. Some of the abstractions are beginning to make sense.
But then I think of alternatives to what the framework proposes; that can
be discouraging.
midrange.com
