-
Notifications
You must be signed in to change notification settings - Fork 14
Why Kotlin?
Francisco Cunha edited this page Jul 22, 2017
·
2 revisions
Although this started out as a pure Java project, I decided to rewrite it in Kotlin. I've been a big fan of the language for a while, and seeing it mature this much made me think that would be a good step to do it. If you haven't taken a look, I'd strongly suggest you doing so. But even with Java, you'll be granted total access to the whole API, so don't worry!
Overall, I'd say that the migration from Java to Kotlin was very positive.
- The old API was totally revisited, and although the main structure stays the same, there were quite a few changes!
- Names are now much shorter and thus cleaner - definitely influenced by Ruby.
- The code became a lot more concise and less verbose - easier to read and follow.
- Stayed totally modular, like it was before.
- Grants a friendly syntax for Kotlin developers, while maintaining complete interoperability with Java.
It's really easy to get Kotlin up and running alongside libGDX. Here are a few resources: