![]() Neither am I here to talk about the small, little, tiny, irrelevant, trivial fact that this language is not exclusive for Android development. And I’ll also avoid going into detail about its expressiveness and let’s-cut-the-boilerplate philosophy, with the great example of the data classes: no getters or setters required, native support for copy(), hashCode() and equals()… or the null-safety the language itself has by default. I’ll just briefly mention its flexibility in terms of allowing type inference. I won’t dwell on the features that make this language the best choice for starting a brand new Android project, and a great one for refactoring or including new features to existing projects, such as being 100% interoperable with Java code (yes, for once, this will be a Plug-and-Play that will actually work). ![]() Today, I’m not going to focus on the technical benefits of Kotlin. Since Google’s Android team announced at the Google I/O keynote 2017 its “first-class support for Kotlin,” or, even a little before that for the bravest developers, adopting Kotlin for Android development has been (and still is) a good idea.
0 Comments
Leave a Reply. |