Lazy thread start is sometimes important. Otherwise, if multiple threads are started and a certain order is needed, they may not start in the right order. I love Kotlin vocabulary titles. Kotlin is fun! 👍
If you are already familiar with programming I would recommend "Kotlin In Action". To get started with android apps you can try google android codelabs but they sometimes contain bad code. Sometimes this code is really awful, and you won't even understand it.
I have a question about these two statements in the video: 2:37 "Lazy initialization still takes the same amount of time as non-lazy initialization of the object on the first access. This means objects which take long to initialize can still block the UI thread if accessed from it." 2:55 "Lazy initialization can be helpful to initialize expensive resources." I don't see how you drew a parallel between the time it takes with lazy and without lazy being the same, and how it's helpful to initialize expensive resources. Wouldn't the benefit simply be that you reduce the cost of initializing it along with other heavy initializations by doing it a later time?
The observer delagate isn't an implementation of the Observer pattern first described here, as it holds no list of dependents as it just calls the provided lambda when property is set. This was really misleading in the video. Just made me really confused instead of helping me understand it.
Lazy thread start is sometimes important. Otherwise, if multiple threads are started and a certain order is needed, they may not start in the right order.
I love Kotlin vocabulary titles. Kotlin is fun! 👍
nice explanation, vetoable is a great name as well
Waiting for this vocab👍
that was perfect
What book do you guys recommend in order to learn Kotlin/Android studio?
If you are already familiar with programming I would recommend "Kotlin In Action". To get started with android apps you can try google android codelabs but they sometimes contain bad code. Sometimes this code is really awful, and you won't even understand it.
I have a question about these two statements in the video:
2:37 "Lazy initialization still takes the same amount of time as non-lazy initialization of the object on the first access. This means objects which take long to initialize can still block the UI thread if accessed from it."
2:55 "Lazy initialization can be helpful to initialize expensive resources."
I don't see how you drew a parallel between the time it takes with lazy and without lazy being the same, and how it's helpful to initialize expensive resources. Wouldn't the benefit simply be that you reduce the cost of initializing it along with other heavy initializations by doing it a later time?
Great!
I liked just because he asked nicely
I knew it! ;)
very usefull
The observer delagate isn't an implementation of the Observer pattern first described here, as it holds no list of dependents as it just calls the provided lambda when property is set. This was really misleading in the video. Just made me really confused instead of helping me understand it.
Which pattern it implements then?
Congratulations 🇹🇷
Next word description should be: Context. I'm eagerly waiting.
Too small code, please next time zoom in when showing the code.
Sure will do! Until next time you can check out the code sniplets here medium.com/androiddevelopers/built-in-delegates-4811947e781f
You need a microscope to watch this on phone