Kotlin under the hood: Understand the internals (Google I/O'19)

[@codinginflow]

Chet Haase is my favorite comedian

[@droidcasts7350]

Romain and Chet presentations are the best, always fun and informative

[@bartekpa]

These two guys always give the best talks :D

[@dimanemets6753]

5 years Android dev, learned at least 5 new things !

[@bug_muzzy]

Awesome duo. Always fun, always concise and informative. Love presentations by these guys.

[@Condog64]

This video is incredibly insightful. I will never forget about Int? needing to allocate every time a new value is assigned. On the other hand, this video also feels like many passive aggressive remarks from Google to Jet Brains around the Kotlin compiler's inconsistencies and oddities. The lambda example actually seems pretty scary.

[@porus10]

Such a piece of crucial information. It's so hard to believe the kind of mess Kotlin creates underneath for providing those extra features to the end developer. Every developer should beforehand dig in a little beneath this syntactical sugar provided by modern languages. And yes, Chet and Romain, always a delight to watch.

[@SaravanaThiyagarajs]

I am hoping someone from Jetbrains will comment on what's happening at 22:05

[@no_fb]

The guy said it himself, it's still experimental. Obviously the code doesn't yet check for wrap-around values and so on. It's just a very bad presentation overall.

[@shyiamnot212]

I don't understand the part of interlude at 10:41,It will help a lot if anyone could explain it for me.Event a little hint would be help.

[@НектоЛохматый]

In Kotlin, we do 10001 comparasions of an integer to a variable of type Int?. As it's been told, Kotlin's Int? is java.lang.Integer under the hood. So, on each iteration we compare a primitive type int to an object of type Integer, and the only way to do this is to wrap the int into a corresponding Integer, like: Integer iAsInteger = new Integer(i); So, we expect 10001 object allocations. But Kotlin optimizes this a little bit by caching instances Integer(0), Integer(1), ..., Integer(127). Unless i gets greater than 127, Kotlin uses the cached java.lang.Integer's instead of allocating new ones.

[@AkshayDave]

Did javap -c "MyClass" work for anyone? When I go to AS terminal, and go to specific folder, and type that command it said class not found

[@comradepeter87]

.. you changed the MyClass to the name of your compiled class, right?

[@AkshayDave]

​@@comradepeter87​I would assumed so ;) It has been almost a year since this one. I will give it another go. "MyClass" was just a stand in.

[@edgeeffect]

This may well be a very good talk, but Google's ridiculous "rockstar" staging is very distracting.

[@shubham0952]

22:05 nice roast

[@stayathomedev3839]

I thought the other speaker's name was Romanian Guy

[@AshutoshTiwari4]

Thumbs Up (Y)

[@donwald3436]

If he steals your slide just steal his lol.

[@no_fb]

Google guys, if you stumble on a few peculiarities in a language under development, talk directly with your partner instead of showcasing them in public and on KZbin. It's lame and unprofessional. After all, Kotlin is your way out of this Dalvik mess of yours.

[@jorgesegundorojas6119]

I'm so angry, why should I keep developing Android applications if at any time and without notice YOU block manufacturers?... even more, why users (and clients) should keep buying Android devices if at any time YOU can make'em "WASTE" their money with this S T U P I D deciscions?.

[@no_fb]

wrong forum, mate

[@hdkloh]

Good bye Kotlin... Welcome Flutter...

[@rgenericson5361]

Dream on!

[@PabloMartinezPiles]

hdk loh 😂😂 you won’t see that

[@aitortilla5128]

Not interested at all in Kotlin. I'll stick to Java.