Why we can't have nice things in Kotlin

Why we can't have nice things in Kotlin | Vsevolod Tolstopyatov

Рет қаралды 11,131

26 күн бұрын

Recording brought to you by American Express. americanexpress.io/kotlin-jobs
Have you ever wondered what challenges Kotlin standard libraries encounter? How is the new API affected by insect collection in 1800s and trade routes with Australia? What twitter polls have to do with Kotlin compiler not working in Turkey? Or maybe how the missing alarm makes us add a new parameter to a function?
In my talk, I'll answer these questions and briefly cover some unusual problems we tackle on a regular basis in Kotlin Libraries.
#kotlinconf

Пікірлер: 27

@dogacel 24 күн бұрын

About topic on capitalization at 1:50, when I was 12, I tried to download mods to play Minecraft and none of them worked even though I followed every instruction. I was able to fix the issue only by changing my computer language to be English. Many years later, I realized why it only happened to me, "Oh......... Makes sense..............................The capital İ"

@reschock713 24 күн бұрын

kotlin is my favorite programming language :)

@anisim 24 күн бұрын

Same here ❤

@tk1576 23 күн бұрын

so much better than java!

@neronguyenvn 20 күн бұрын

sometimes I can manage to get enough motivation to play some more kotlin in my pet projects, but I still feel I will scared of stuffs gonna happen there; I would only comfortable with my familiar skills or framework; what should I do

@wayluke 19 күн бұрын

And you use it to....? Andoird Dev? Back end server?

@wayluke 19 күн бұрын

@@tk1576 So you use it to replace those domains which use java before? Or you use it every where with kotlin/native?

@songyifan6531 24 күн бұрын

Funny and attractive talk, love this one!

@krellin 24 күн бұрын

Experienced engineers don't mess with timezones and use a timestamp long, do all the compute with it and then convert to strong in front end

@h4m74ro 24 күн бұрын

If possible, do it. But for something like calendar apps or future events, don't do it.

@krellin 24 күн бұрын

@@h4m74ro you do it for everything, no exceptions, calendar or not, if you need to do some sophisticated crap like fintech tends to do, or simply say go to last day of month... feel free to temporarily convert to date time or jodat time whatever but your main format should always be timestamp. Put assertions that validate that your modifications make sense but the moment you start using Date alike formats in Dbs or pass them around everything goes to shit. Once some legacy is created using that it never goes away.

@tomhejda6450 22 күн бұрын

So that you set your alarm -- when flying -- to 7am before your phone realized you're crossing 3 timezones, only for it to ring at 10am.

@MarkAndrachekJr 22 күн бұрын

This is the way. I have spoken.

@h4m74ro 22 күн бұрын

@@krellin User sets a alarm at noon 12:00. When you save that as timestamp instead of 12:00, it will be wrong after changing time zones. Or user saves a meeting in his calendar for next year 1st of july at 10am and is based in Germany, that is 2025-07-01T10:00:00+02:00. Again, if you would use timestamp instead, you have a bad time when unexpected things happen, like EU decides to abolish daylight saving time. Even the leap seconds every few months will cause a small discrepancy. I'm not saying, save Date objects, only string representation in ISO format. That works wherever you are and on any device.

@thedeemon 21 күн бұрын

Daylight Saving Time adds more light time to evenings in summer, not in winter. It makes winter days go dark earlier. At least in northern hemisphere. I never thought about how it works in New Zealand. I guess it's much crazier there.

@ALONEWILL 23 күн бұрын

I moved from swift to kotlin for my leetcode and figured out how strong is Kotlin , never discovered this during my last 4 yrs with kotlin in android.