I like kotlin corutine very much, but I don't understand how to use progress update like Asynctask, I have asked every where but not getting proper response. So, please inform me, if kotlin corutine support determinant progress bar or not. Thanks.
I might be a noob, but I can tell the code at 33:26 z going to be runtime problematic. If the function observeLocation will be called more than once, we are going to have multiple callbacks, each with its own job reference, which kinda defeats the purpose of it being there in the first place (Its canceled if there is another running job). But again, I am so new to coroutines
rxjava does all this and much more, it has such a comfortable operator dictionary. Why doesn't google promote rxjava still? Coroutines are native yet inferior to rxjava
1) It lets you write asynchronous code in a synchronous way unlike rxjava where you use callbacks. 2) Thread are expensive. Coroutines (Generators) are also called light weight thread that can perform multiple task (multitask by pausing and resuming functions at set points) typically (but not necessarily) within a single thread (timesliced).
I believe that Flow type is a game changer, using it RxJava isn't a superior anymore. But I'm also sorry to see RxJava is leaving the scene, but I'm happy the pattern remains.
7:15 Suspend functions
8:55 async
9:18 launch
10:52 Jobs
11:50 Scopes
16:10 Create coroutine scopes for lifecycleOservable objects
18:25 Cancellation
20:02 Exception
22:36 Dispatchers
thanks mate
Aside from the awesome talk, I really want to know how they created the slides.
Me too. Very nice slides.
slides.com
I like kotlin corutine very much, but I don't understand how to use progress update like Asynctask, I have asked every where but not getting proper response. So, please inform me, if kotlin corutine support determinant progress bar or not. Thanks.
I might be a noob, but I can tell the code at 33:26 z going to be runtime problematic.
If the function observeLocation will be called more than once, we are going to have multiple callbacks, each with its own job reference, which kinda defeats the purpose of it being there in the first place (Its canceled if there is another running job).
But again, I am so new to coroutines
Why do we need a suspend retrofit function? Retrofit already runs in a background by default.
why didn't he mention context for network call like dispatcher.io? while launching...
To bad u couldn't put all the directions in one action by the push of what ever your issue is.
It was "RTFM" instead of "RTM"
What that means?
rxjava does all this and much more, it has such a comfortable operator dictionary. Why doesn't google promote rxjava still? Coroutines are native yet inferior to rxjava
1) It lets you write asynchronous code in a synchronous way unlike rxjava where you use callbacks.
2) Thread are expensive. Coroutines (Generators) are also called light weight thread that can perform multiple task (multitask by pausing and resuming functions at set points) typically (but not necessarily) within a single thread (timesliced).
I believe that Flow type is a game changer, using it RxJava isn't a superior anymore. But I'm also sorry to see RxJava is leaving the scene, but I'm happy the pattern remains.