19:45 I’m all about minimizing code on slides but you could have easily added a Val cats=mutableListOf(Cat(…), Cat(…)) to know what we are working with!
36:23: "Trying to tell us to use Option rather than nullable because... monads." That's just not true, the fact that it exists doesn't mean that it's encouraged over nullables. If anything, the opposite is true for what the arrow documentation suggests. Go to their docs on `learn/typed-errors/nullable-and-option/#conclusion` which states the exact opposite of what was mentioned in this talk. 37:30: "Bending language features to find a way to achieve the goal". Assuming this is regarding the use of coroutines to handle returning quickly from functions, I don't think "bending" is the right word for it. Maybe watching the video "Coroutines Beyond Concurrency by Alex Semin" from KotlinConf will give some inspiration as to how coroutines are not just this concurrency tool and it stops there. 14:47: "And we're still waiting". Isn't the solution the slide that was presented at 37:41?
13:47 trying to be funny here and it should have been skipped bc we are not Java programmers and don’t need to hear about semicolons, ok? Noisy capricious Reference that only confuses the listener
I had a blast at KotlinConf. Thanks to all the people who made it such a great event.
19:45 I’m all about minimizing code on slides but you could have easily added a Val cats=mutableListOf(Cat(…), Cat(…)) to know what we are working with!
21:03 android phones used to be low powered but not anymore lol
These guys are a hoot
36:23: "Trying to tell us to use Option rather than nullable because... monads." That's just not true, the fact that it exists doesn't mean that it's encouraged over nullables. If anything, the opposite is true for what the arrow documentation suggests. Go to their docs on `learn/typed-errors/nullable-and-option/#conclusion` which states the exact opposite of what was mentioned in this talk.
37:30: "Bending language features to find a way to achieve the goal". Assuming this is regarding the use of coroutines to handle returning quickly from functions, I don't think "bending" is the right word for it. Maybe watching the video "Coroutines Beyond Concurrency by Alex Semin" from KotlinConf will give some inspiration as to how coroutines are not just this concurrency tool and it stops there.
14:47: "And we're still waiting". Isn't the solution the slide that was presented at 37:41?
dont flood my feed, multiple videos
13:47 trying to be funny here and it should have been skipped bc we are not Java programmers and don’t need to hear about semicolons, ok? Noisy capricious Reference that only confuses the listener