I recently ran across an article that does a great job of explaining the thought process when considering adoption of a new programming language. The article explains why Kotlin was chosen and compares its value to other languages having more maturity. Often times, it can be a challenge to get buy-in for any new language or technology within an organization. Most of the time, slow adoption and/or exploration is due to lack of interest in change or simply not wanting to incur risk through change. However, in some cases, adoption of a new language can pay-off due to the features provided and improvements made over existing languages. When a new language is applied and adopted properly, this can translate to more efficiency and higher quality business solutions for an organization. In my opinion, Kotlin is worth the risk to start exploring and adopting. Articles like the one below, along with illustrating benefits through proof-of-concepts, go a long...
The official Kotlin style guide has been published at kotlinlang.org Kotlin Official Coding Conventions For those not familiar with style guides, it provides best practices & recommendations for a language's naming rules, formatting, documentation, etc. It can make your source deliverables much more consistent, readable, and efficient. When working with other developers it becomes important to follow some level of coding standards that can be enforced through code reviews. If you use IntelliJ IDEA for your Kotlin development, there is a formatter available that matches the published style guide. This assists with the coding conventions while developing in IntelliJ IDEA. 1. Install the Kotlin plugin version 1.2.20-eap-33 or newer Kotlin Plugins 2. From IntelliJ menu, navigate using File -> Settings -> Editor -> Code Style -> Kotlin 3. Use the " Set from " link and select " Pr...