Martin is an enthusiastic software engineer building and operating microservices in the JVM stack using Kotlin. Currently working for Albert Heijn in the role of DevOps engineer.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Steep learning curve?
That was not my experience.
You should be able to get starting quite easily by git cloning the Kotlin Koans and fixing the unit tests in Intellij github.com/Kotlin/kotlin-koans
What task are you solving? Yes, Kotlin is fresh and new and superawesome. But Java is as well. Performance-wise it is the same as both compile to JVM.
For me there are no big improvements to move from Java to Kotlin. I prefer the more verbose way Java is doing things.
I tried to get used to Kotlin but it has a steep learning curve.
It really depends on the task that defines the toolkit being used to solve the problem.
Steep learning curve?
That was not my experience.
You should be able to get starting quite easily by git cloning the Kotlin Koans and fixing the unit tests in Intellij
github.com/Kotlin/kotlin-koans
Additionally, I feel like a lot of the issues mentioned are already solved in new versions of Java
Can't agree more, it really varies and depends. I prefer to stick to Java if it doesn't make too much difference