Sharing Top Content from the Angular-sphere.

3 reasons why you should follow Angular-In-Depth publication

  • However, if you’re writing a large application, possibly a platform, you have to know the framework at the deeper level.
  • Depending on the complexity of the application you’re working on I’d argue that you have to posses a solid knowledge of the core concepts like views, change detection and injectors and understand their mechanics.
  • Unfortunately, when I started with Angular there was no detailed information about injectors hierarchy, views, change detection and other core concepts.
  • And the problem of course is not exclusive to Angular but also extends to other front-end technologies related to Angular like RxJs and Webpack.
  • And so I started Angular-In-Depth publication with the goal to provide these unique in-depth insights into the internals of all technologies related to or used inside Angular — the framework itself, RxJs, Webpack, TypeScript, FireBase etc.

Angular is a great framework. It makes many web development tasks that used to be tricky and time-consuming a breeze. But it’s also a complex framework and new features are being developed at a rapid…

Angular is a great framework. It makes many web development tasks that used to be tricky and time-consuming a breeze. But it’s also a complex framework and new features are being developed at a rapid pace. The official documentation has recently caught up with the extensible amount of functionality the framework offers and is now sufficient to understand major concepts and create a middle size app.

However, if you’re writing a large application, possibly a platform, you have to know the framework at the deeper level. Depending on the complexity of the application you’re working on I’d argue that you have to posses a solid knowledge of the core concepts like views, change detection and injectors and understand their mechanics. But as it currently stands there’s no information about the internals.

directive that destroys and recreates the view.

Unfortunately, when I started with Angular there was no detailed information about injectors hierarchy, views, change detection and other core concepts. I haven’t done much searching in the past six months but I’m willing to bet that most of the information that you can find in the articles published in Angular-In-Depth publication are not available anywhere else.

And the problem of course is not exclusive to Angular but also extends to other front-end technologies related to Angular like RxJs and Webpack.

modules. It simplifies working with asynchronous code and enables interesting reactive architectures. And just as with Angular it’s a pretty complex…

3 reasons why you should follow Angular-In-Depth publication