I have friends who work at the biggest bank in Latin America, where most backend stuff used to be Java. Nowadays all new code is written in Kotlin.
this post was submitted on 08 Jul 2023
4 points (100.0% liked)
Programming
16975 readers
1288 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
I've been using it server side (haven't touched android for ~12 years) for almost 7 years now. It's fantastic.
Yes, I write SpringBoot microservices and IntelliJ plugins using Kotlin. Any new code is Kotlin, but there is still a ton of Java, which I don't consider "legacy", since it works, and if I can sanely add Kotlin when necessary, I don't see the need for "full rewrite".
You may get more traction by asking the Kotlin community
Legacy code is just code inherited from developers that are no longer around. It's quality has nothing to do with its age.
the developers don't have to of left the team to make it legacy code
Lots of people do, just look at all the server libs for kotlin.
Loved using it when I took a brief stint as an Android dev at my company. Later talked to my tech lead to see if he was open to me writing future backend developments in Kotlin but he said it would be too much unneeded work to get the entire team to learn a new language to keep the backend maintainable.
Last job, we started writing mixing bits of Kotlin in an otherwise mostly-Java in a monolithic Spring-based service. Good experience.
I don't use it right now, but two years ago I helped a team incrementally adopt Kotlin in a ten year old java/spring/mybatis codebase. We didn't have any android experience and in the initial few months mostly used kotlin as a better java, avoiding features that would prevent us from switching back to java if needed.
But it worked pretty well - we didn't face much resistence from people experienced with java because they could still continue to benefit from their jvm familiarity, and the language was approachable to new folks who joined us. It also helped that we could just copy paste java code into a .kt file and intellij would convert it to kotlin.
We didn't venture into kotlin's js/native targets but for jvm it worked out great for us.
I don't know if it's popular but a few companies use it for backend servers instead of using Go or Node.js. It's a language that I really enjoy even if I have never used it professionally.
I retired now, but I still write code for my blog. I totally prefer to write with Kotlin. Java just feels clunky to me now.
Kotlin is used as the base of TeamCity's DSL, so I have to use it from time to time at work to configure build pipelines.
But I have never used it to build anything too complicated.
Seems like a massive step up from Java in terms of developer experience. But that's obviously just an opinion.