C# or Kotlin? Which one should I learn? What do you think?

19 Tem 13:56

Who knows, maybe in the future you'll be discussing nothing more than the differences between inheritance in C# and extension functions in Kotlin, all while using IDEs with "multi-language refactoring" buttons. You might even be developing an IDE yourself! If we strip it down to the basics when comparing C# and Kotlin, both stand out as the most mature languages in the JVM and .NET ecosystems. If your future plans include desktop apps, game engines, or enterprise systems under heavy load where performance is non-negotiable, C# has a clear advantage. Why? Thanks to Unity and .NET’s IL-based runtime with JIT-compiled code, C# enjoys a natural optimization edge over Kotlin/JVM. Plus, features like pattern matching, records, and nullable reference types introduced in C# 7+ have made the language cleaner and safer. On the Kotlin side, its strength lies in clarity. Designed to address Java’s pain points, Kotlin has evolved into a truly multi-platform language with support for JVM, JavaScript/JSX-like (Kotlin/JS), and Native (Kotlin/Native). If you're working on Android and backend development using the JVM, and you want to use the same language across both server and mobile with the same team, Kotlin is a far more compelling choice. The language itself also boasts a modern, readable syntax compared to Java. In the end, the decision shouldn’t hinge on the platforms the languages target, but on your own future goals. If you want to touch both desktop apps and the mobile world, learning both could open doors. With C#, you can dive into Unity game development, and with Kotlin, you can build Android apps alongside backend JVM services. Both are in high global demand, but which one you choose ultimately depends on your ecosystem needs!

19 Tem 16:12

A few years ago, when I decided to learn a new programming language, I was stuck in the same dilemma as you. Actually, it wasn’t so much about platform preferences as it was about my project goals. I initially tried learning Java, but I found myself inefficient wrestling with its complex syntax. Then I discovered C#, and thanks to the tools in Visual Studio, I built a simple console app in a week and could focus on the project I loved. When I switched to Kotlin, my Android development process changed completely—thanks to null safety and functional features, I made fewer mistakes and my code became more readable. The biggest lesson I took from this experience is that you should choose based on your goals. If you want to build desktop apps, games, or enterprise-level web applications, C#’s tight integration with the .NET ecosystem is a huge advantage. But if you’re focusing on mobile, Kotlin’s Android Studio integration and its cleaner take on modern Java can make a real difference. As for future prospects, I think both have solid foundations—C# will remain strong in the corporate world thanks to Microsoft’s support, while Kotlin is now being adopted not just for Android but also for backend and multiplatform development. In short: if you’re going the Windows/Unity route, go deep with C#; if Android is your path, dive into Kotlin. Even knowing both at a basic level can open a lot of doors down the road.