The Advantage of RxJs is: once you are in the RxJs World with a creation Observable (interval, of, range,...) you can stay in this world for all your logic and when you want to run the RxJs Pipeline you built (RxJs programming is building a Pipeline of functions (operators) you subscribe to the pipeline!
I agree you should use Angular in the simplest possible way! (do not use all the whistles and bells of Angular from the begin of your project) Have a simple Angular Mental Model: Angular is 5D: Directives - Data Binding - Dependency Injection - Decorators - Dirty Checking! or Angular is a huge Template Engine: Angular starts with the Template (the my-component.html is not HTML it is a template with ... !
i agree with you, that not everything needs to be pressed in the rxjs pattern. single one-time calls are perfect for promises. i also agree on the less modules. it leeds to over-engineering
I have to disagree with the "There are no bad practices" point. There are, and I have been screwed over by some in quite a few legacy projects that I need to maintain. The KISS principle is great, but I think many people mess up the two concepts of "simple" and "easy," and I am afraid that Nir's first part on modules is a bit misleading here. When the problem that an app is trying to solve is simple, keeping things all together is ok. Heck, you may not even need a framework for that, let alone something like Angular. However, when the problem and its business domain get complex, one has to split things up, either vertically or horizontally, or most likely, both. You don't include everything in the initial bundle (putting everything in a single module) because it's easy. You don't include a bunch of function calls that deal with business logic in the template because it's easy. These easy practices hurts maintainability, and I don't think we should lower the bar when it comes to architecture just because we are dealing with the frontend.
at 25:00 using simple promises helped in downloading file. Because it was one time thing and single. There was no way to use async pipe for it in the template. If I use promise for this purpose, I don't need to clean it.
This talk is honest. May be a little bit too honest coming from an Angular insider. But every point Nir says is blatantly true. The angular team seems to be focussed on complicating Angular more and more to push it to do all things at once making it difficult to learn and to code... But the only way to make angular better is to reduce the complexity and leave it to the developers to add complexity where and when needed. Just by reducing the dependency on RxJS and better managing the change detection and removing unwanted dependencies Angular will be 100 times better than the other frontend frameworks/libraries out there.... But it seems unlikely...
I kindly disagree with the RxJS part. I hope they can use the reactive part of RxJS more internally for a more performant, more localized, and easier-to-learn reactivity system and ditch zone.js. The choice of event-driven change detection has its background but data-driven is just simpler and easier to get good performance. The Angular team is going to rework the reactivity system it seems, based on the talks from the latest ng-conf.
Oh RxJs is so evil and soooo dificult Mi mi mi...All crybabies and just bad developers. RxJS is a great tool. Frontend Development is by nature reactive thats why RxJs is a great fit!!!
![[LIVE] : ONE ลุมพินี 86 | คู่เอก "คมเพชร vs ชาติพยัคฆ์"](http://i.ytimg.com/vi/m3q_dRYDuU8/mqdefault.jpg)
The Advantage of RxJs is: once you are in the RxJs World with a creation Observable (interval, of, range,...) you can stay in this world for all your logic and when you want to run the RxJs Pipeline you built (RxJs programming is building a Pipeline of functions (operators) you subscribe to the pipeline!
I agree you should use Angular in the simplest possible way! (do not use all the whistles and bells of Angular from the begin of your project)
Have a simple Angular Mental Model: Angular is 5D: Directives - Data Binding - Dependency Injection - Decorators - Dirty Checking!
or
Angular is a huge Template Engine: Angular starts with the Template (the my-component.html is not HTML it is a template with ... !
I am scared to disable the zone-js in the existing applications.
Angular-KISS should become an Angular Community!
i agree with you, that not everything needs to be pressed in the rxjs pattern. single one-time calls are perfect for promises.
i also agree on the less modules. it leeds to over-engineering
I have to disagree with the "There are no bad practices" point. There are, and I have been screwed over by some in quite a few legacy projects that I need to maintain.
The KISS principle is great, but I think many people mess up the two concepts of "simple" and "easy," and I am afraid that Nir's first part on modules is a bit misleading here. When the problem that an app is trying to solve is simple, keeping things all together is ok. Heck, you may not even need a framework for that, let alone something like Angular.
However, when the problem and its business domain get complex, one has to split things up, either vertically or horizontally, or most likely, both. You don't include everything in the initial bundle (putting everything in a single module) because it's easy. You don't include a bunch of function calls that deal with business logic in the template because it's easy. These easy practices hurts maintainability, and I don't think we should lower the bar when it comes to architecture just because we are dealing with the frontend.
at 25:00 using simple promises helped in downloading file. Because it was one time thing and single. There was no way to use async pipe for it in the template. If I use promise for this purpose, I don't need to clean it.
This talk is honest. May be a little bit too honest coming from an Angular insider. But every point Nir says is blatantly true.
The angular team seems to be focussed on complicating Angular more and more to push it to do all things at once making it difficult to learn and to code...
But the only way to make angular better is to reduce the complexity and leave it to the developers to add complexity where and when needed.
Just by reducing the dependency on RxJS and better managing the change detection and removing unwanted dependencies Angular will be 100 times better than the other frontend frameworks/libraries out there.... But it seems unlikely...
I kindly disagree with the RxJS part. I hope they can use the reactive part of RxJS more internally for a more performant, more localized, and easier-to-learn reactivity system and ditch zone.js. The choice of event-driven change detection has its background but data-driven is just simpler and easier to get good performance. The Angular team is going to rework the reactivity system it seems, based on the talks from the latest ng-conf.
Oh RxJs is so evil and soooo dificult Mi mi mi...All crybabies and just bad developers. RxJS is a great tool. Frontend Development is by nature reactive thats why RxJs is a great fit!!!