You have what comes across as a very natural ability, and great analogies, for explaining these very useful, but often confusing, technical topics. I've found myself coming back to your videos repeatedly (share-replay). I know 'I'd appreciate some minimal, but end-to-end, code examples to refer to (e.g. a service to store (and share) selected state across components: view/edit/navigation/breadcrumb etc), but appreciate the time required to produce something like that. Clearly you are the perfect person to be building an LMS! - A natural teacher.
I don’t, but I’ve returning from a bit of a break and I’m the time I’ve been gone, my programming videos have gathered a lot of attention. I’m going to make some RXJS videos in response to many comments and we’ll see if that leads into an Angular course.
Just wondering if we use ReplaySubject with a type of Book[] as the generics, does it automatically add null or undefined to it? Regardless whether it does or not, I don't think Replay is a lot better than Behavior subject. Because it forces the users to be aware of the type. If it can never be null then instantiate with empty array. If we instantiate with null then we have to include null. For for ReplaySubject, we don't know. If it always add null to the type then we always have to handle that throughout our code base. If it does not atuo add null to the type then we are likely to get our favorite null pointer. So base on what is discribed in the vid, I don't think we should use ReplaySubject. If possible, stick to BehaviorSubject, yes we might need to instantiate with null but so what, the benefit is a much safer application.
Sure. Here’s an exercise. What can I use to replace “var” in this sentence? “I wrote a varter about when I drove a Chevrovarte to go outvar shopping.” 😜
Akil Montrope Yes. When you said “let” us think about... I thought you were making a joke. In seriousness, let can also be used and it was an error to not mention it as an appropriate option. www.typescriptlang.org/docs/handbook/release-notes/typescript-1-4.html#let-declarations
You have what comes across as a very natural ability, and great analogies, for explaining these very useful, but often confusing, technical topics. I've found myself coming back to your videos repeatedly (share-replay). I know 'I'd appreciate some minimal, but end-to-end, code examples to refer to (e.g. a service to store (and share) selected state across components: view/edit/navigation/breadcrumb etc), but appreciate the time required to produce something like that. Clearly you are the perfect person to be building an LMS! - A natural teacher.
Great tutorial. You have a knack of explaining difficult concepts
Hey, thank you so much!
thx man, plz create more angular tutorials
thank you for the amazing videos
Veeerryyy interesting about the replay subject approach - I'm gonna give it try - thanks man 👍
Update : It worked! Big thanks NBB
It’s difficult to find clear concise tutorials that illustrate the strength of the Angular platform. Yours is one of the few ones to do so in 11 mins.
Wow, what a compliment! Thank you!
Nice, thanks. If you share a repo with the code for each video that would be great to take a closer look.
Pure gold !
I like literally everything u do .. And what microphone and camera name u use ..
Well explained...👍
hari prasad thank you so much! Sometimes I worry I’ll receive criticism for over simplifying. Got to find the right balance.
Hello @NeverBenBetter,
Do you teach full online video course to Angular?
If YES, it would be great.
If NO, can you pls make some depth video online!?
I don’t, but I’ve returning from a bit of a break and I’m the time I’ve been gone, my programming videos have gathered a lot of attention. I’m going to make some RXJS videos in response to many comments and we’ll see if that leads into an Angular course.
Thanks
Just wondering if we use ReplaySubject with a type of Book[] as the generics, does it automatically add null or undefined to it?
Regardless whether it does or not, I don't think Replay is a lot better than Behavior subject. Because it forces the users to be aware of the type. If it can never be null then instantiate with empty array. If we instantiate with null then we have to include null.
For for ReplaySubject, we don't know.
If it always add null to the type then we always have to handle that throughout our code base.
If it does not atuo add null to the type then we are likely to get our favorite null pointer.
So base on what is discribed in the vid, I don't think we should use ReplaySubject. If possible, stick to BehaviorSubject, yes we might need to instantiate with null but so what, the benefit is a much safer application.
Would be good if you can just call it union type since that's the official term
this is why im moving to React.js
Let us think about another option than var.
Sure. Here’s an exercise. What can I use to replace “var” in this sentence? “I wrote a varter about when I drove a Chevrovarte to go outvar shopping.” 😜
You could use 'let' from ES6 right?
Akil Montrope Yes. When you said “let” us think about... I thought you were making a joke.
In seriousness, let can also be used and it was an error to not mention it as an appropriate option. www.typescriptlang.org/docs/handbook/release-notes/typescript-1-4.html#let-declarations
@@neverbenbetter8225 It was a joke, but not by Akil!
10:19 where do these functions get called from? When do they get called? this.doOnChange() and this.whenSynched()
I like literally everything u do .. And what microphone and camera name u use ..