For fuck's sake, people still think that way? Also, I'm sorry that it is coming to this.

Damn you qwerty keyboard and the English language! Why do i and o need to be next to each other in the keyboard layout and why both in and on are valid prepositions in English?

@japchap As an Android developer, that is the source of most frustration I have. There are some cool things in newer versions of Android (Lollipop and newer), but there are still some not-so-old devices that run really old version of the OS. On iOS, I can count on iOS 9 being supported by almost all devices actively used out there. Think about it, iPhone 4S, which was released 5 years ago, can run iOS 9 just fine. An Android device released in 2011 most probably can't run Marshmallow.

//

Good question. Maybe none, maybe some. We'll see. But I like the fact that in Kotlin everything does not need to be a class. Which is frustrating sometimes.

Excellent points. I truly hope that sensible people will resist the stupidity that may rise.

I find it depressing how those ultra-religious people (all-around the world, to be fair) seem to pick and choose parts of their religion that they want to impose to others while ignoring other, more important teachings.

// @skematica

I meant that I can now implement Android stuff quite fast with Java and that I feared that making Kotlin code interoperate with Android frameworks and libraries would slow me down. That fear seems to be unnecessary, Kotlin is (almost) 100% compatible with Java, so I can keep up the pace.

Wrote some Javascript after a long, long break.

@thrrgilag I think I will write a simple test app first to get an idea how the integration with Android frameworks work. Then I will make the decision whether to write the remaining functionalities of the 10C app in Kotlin or not.

Hmm… I wonder if I should try out writing (at least some parts of) my 10C Android app in Kotlin. I just fear that introducing a new language/system to the mix will slow down the progress way too much.