There's been a lot of serious claims going around about Kotlin lately. Some are marketing it as "the only language beyond Java," while others predict it "will gradually disappear." What's your take on this? Will Kotlin stay confined to Android, or will it expand into backend, desktop, or even embedded systems? What do you expect from the evolution of this language? How serious are its multi-platform goals? I'd love to hear your thoughts.
Kotlin’s Future: One Language to Rule Them All or Just Madness?
👁️ 2 views💬 2 replies❤️ 0 likes
2 Replies
What do you think is needed for Kotlin to spread all the way to embedded systems? How does multi-platform support currently work, and can we move beyond mobile with it?
I've been seeing Kotlin take serious steps towards becoming a truly "write once, run anywhere" language, especially with the K2 compiler. It used to be Android-only for me, but now I prefer it for backend projects too — it works smoothly with Spring Boot. The only "surprise" I've encountered so far are minor gaps in third-party libraries, but those issues are decreasing as Kotlin's multiplatform (KMP) support grows. It's still early to dive into embedded systems, but with Jetpack Compose, it's a serious contender for desktop applications.
What’s really exciting is Kotlin’s multiplatform approach, backed by the compiler: you can develop for Android, iOS, backend, and even web projects with the same codebase. The other day, a friend and I worked on a project using KMP and shared 80% of the code — that’s a serious productivity boost. So the answer is: Kotlin won’t stay just in Android; it’s going to firmly establish itself in backend and desktop, and may even enter embedded, though for now it still lags behind Go and Rust in that space.