From 35e24b92639fd671ddb8a9200c816619f1a3ced4 Mon Sep 17 00:00:00 2001 From: wgroeneveld Date: Thu, 19 Aug 2021 11:58:56 +0200 Subject: [PATCH] kotlin rose tined glasses: typo --- content/post/2021/08/the-kotlin-rose-tinted-glasses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/post/2021/08/the-kotlin-rose-tinted-glasses.md b/content/post/2021/08/the-kotlin-rose-tinted-glasses.md index eea046d1..74d57fdd 100644 --- a/content/post/2021/08/the-kotlin-rose-tinted-glasses.md +++ b/content/post/2021/08/the-kotlin-rose-tinted-glasses.md @@ -14,7 +14,7 @@ My Kotlin rose-tinted glasses broke. I am not saying I developed a strong disliking for the language: rather, I'm starting to miss Go's simplicity. But for Android-based app development, Kotlin is the recommended way to go, so I plodded on. Perhaps more cautiously. As you compile your Kotlin code, you generate JVM-compatible bytecode. The problem is, sometimes, that generated code is not what you want. Some situations even reminded me of troublesome times where we once thought relying on Spring Boot and scaffolding was a great idea. Code generation is always asking for trouble, especially if that duplication hurts your eyes and you'd like to refactor it out. -A few simple examples to demonstrate the issue. Suppose I want to write a static method on a class. That's impossible: Kotlin does not know `static`. The JVM does, however, and thus, translations are in order, and you have to learn to new syntax: +A few simple examples to demonstrate the issue. Suppose I want to write a static method on a class. That's impossible: Kotlin does not know `static`. The JVM does, however, and thus, translations are in order, and you have to learn the new syntax, which basically does the same thing: ```kt data class Kitten(val name: String, val age: Double) {