Re:The Hitchhiker's Guide to Kotlin
by travisgriggs on Wednesday September 22, 2021 @02:14AM
(#28613559)
I do a bit of Kotlin on Android. Two decent sized native apps. We do no Java, but use some Java libraries.
I like Kotlin enough. But I don’t love it. Like Swift (and maybe Python yet), it’s a language that tacks on more stuff every release in interest of grabbing yet another programming model niche. It’s like a Swiss Army knife with a _lot_ of blades and gadgets and tools. It’s like a VC funded start up that throws features at the wall to see what sticks and placates.
I want my languages to be built on simple unifying principles. Kotlin’s principles often seem to be:
- we get rid of boilerplate . . . when ever we can, but not really consistently. Removing boiler plate trumps consistency in code communication
- you have a rising idea over there in your ecosystem? we will add it in ours
- by keeping our documentation very simple (nee spartan), we can claim our language is simple
This year it is coroutines, tomorrow it will be sealed classes, or who knows.
I like Kotlin enough. But I don’t love it. Like Swift (and maybe Python yet), it’s a language that tacks on more stuff every release in interest of grabbing yet another programming model niche. It’s like a Swiss Army knife with a _lot_ of blades and gadgets and tools. It’s like a VC funded start up that throws features at the wall to see what sticks and placates.
I want my languages to be built on simple unifying principles. Kotlin’s principles often seem to be:
- we get rid of boilerplate . . . when ever we can, but not really consistently. Removing boiler plate trumps consistency in code communication
- you have a rising idea over there in your ecosystem? we will add it in ours
- by keeping our documentation very simple (nee spartan), we can claim our language is simple
This year it is coroutines, tomorrow it will be sealed classes, or who knows.