03:36 #01 Explosive Placeholders 04:33 #02 Semantic Validation 05:59 #03 Anything and Nothing 08:54 #04 Let 10:50 #05 Multiline String Literals 11:50 #06 Lazy but Speedy 13:12 #07 Code Block Measurement 13:49 #08 Deprecation Levels 15:03 #09 Deprecation Replacements 15:58 #10 Erasing Erasure

@bcut

5 жыл бұрын

thanks +Ersin Ertan

@theapache64

5 жыл бұрын

@Devoxx You should add this timeline to the description (y)

@ayudakov

4 жыл бұрын

Thank you!

@holdenwilder4506

2 жыл бұрын

I dont mean to be off topic but does someone know a trick to get back into an Instagram account? I was stupid forgot the account password. I would appreciate any assistance you can give me

@ramkrishnasarma1171

2 жыл бұрын

@@holdenwilder4506 k

Years later and still informative, thanks a lot.

#10 is really cool. Well, all of them are, but I didn't know about this one :)

Great video. Concise and to the point yet a wealth of information shared. Thank you

Finally my KOTLIN search is over. Great Video. Great Format. Easy to see on chromecast.

Excellent video. Well done.

All hail lord Jake Wharton!

Great tricks! thanks Jake.

This is very good, I watch it three times to learn every point

This talk was a thing of beauty. Well done.

didn't know #10. thanks!

Amazing tutorial

Awesome video! I was thinking about the ?.let thingy, now i understand why it is preferred way to work with Kotlin's volatile var variables, instead of if (var != null), i would put several likes if i could.

@felipepereira3061

5 жыл бұрын

Good to u if u onderstood the concepts...lol

In my case, annotation for deprecation sounds fairly useful!!

@azizbekrasulmetov9293

Жыл бұрын

when can we use it? Why one would need it? I coulnt get it.

@turastory

Жыл бұрын

Well, it's fairly old one so I couldn't remember what I thought back then but here are some use cases I think.. 1. Library authors - definitely the changes in the library that might not compatible with the older ones should be noted before the changes were made. Many parts of Android framework uses deprecation annotations, for instance. 2. Large codebase where the author of the code is different from the user of the code. It is similar to the first one.

Even after 4 years of this video, I can bet that 99% of the Android developer do not know about all 10 things. Even I am working in Kotlin since 2018 and I did not know 4 things from this video.

butterknife: I'm following u.

I am also interested in how he design the slide. It is very concise and intuitivr.

today you made me fan of yours ..... it's really really useful thing's man i am going subscribe now with bell icon and also like your all videos keep making content like this ... anyway i am Android developer and i want to learn advanced Android like .....Cred app ... guide me how can i archive performance like Cred

13:40 its actually measureNanoTime{}

So nervous 😳

Wait, if you wanted to access name like user.name instead of getters why not just make name public?

@tom01b

5 жыл бұрын

( ͡° ͜ʖ ͡°) property access still uses the mutators and accessors (whether they be manually defined or auto generated)

@illusion9423

2 жыл бұрын

If anyone else sees this. It's because attributes have a thing called properties that you can use to remake a getter or a setter. You can also use it to make the setter private. Those things are not in Java, hence with Java it's unsafe because later you might make your getters do something else besides returning the variable, but in Kotlin, because you can always change them with properties, it is safe

THAT'S 20 ISH MINUTES!!#!#+#(#(#(#

7 out of these 10 things are literally stolen from Scala. Kotlin is cheap Scala clone.

I dont watched the whole vid since you don't show "T R I C K S" you just repeat kotlin idioms, so you do clickbaiting. Shame on you.