Looking at the flow so far, I'm guessing that there may be a future where everything from apps to the Web will be completed with Kotlin and Swift (and JS). I will write below what it means.
As a recent trend, the backend uses a common API, An architecture that expresses each of the Web, iOS App, and Android App on the front side has been sought.
May 2017 Kotlin becomes the official language for Android. https://blog.jetbrains.com/kotlin/2017/05/kotlin-on-android-now-official/
And it is presumed that the momentum to use Kotlin will increase in the future for the following reasons. -Nullpo crash, which is the biggest cause of crash, can be suppressed. -You can use existing Java code together.
Kotlin and Swift have quite similar language specifications, so you can use a lot of code logic and writing style (of course, each architecture is different, so consider that)
Therefore, now that Swift has become mainstream in iOS, there are many advantages to introducing Kotlin considering the situation where you work as an engineer for both Android and iOS.
Since January 2017, Spring Framework is also compatible with Kotlin. https://spring.io/blog/2017/01/04/introducing-kotlin-support-in-spring-framework-5-0
And, as in 2., it is presumed that the momentum to use Kotlin will increase in the future for the following reasons. -Nullpo crash, which is the biggest cause of crash, can be suppressed. ・ Fast processing (compared to other web development languages)
Also, from 2. and 3, when the app engineer moves to the back end, There are few new catch-ups of language specifications, and know-how can be introduced to the back end, which is a great advantage.
Since Java has decided to support the released version only for half a year after its release, it is speculated that the use of Java will be avoided in the future. http://d.hatena.ne.jp/nowokay/20171007
In the first place, when considering what the intention of adopting Kotlin for Android is, I think that it is to eliminate Java dependence. The reason is that Android has been sued by Oracle for Java. https://japan.zdnet.com/article/35089816/
With that and the problem of EOSL in 5., maybe Google will push Kotlin more? It is inferred. Also, when that happens, the ultimate VM for Kotlin will be released by Google, and even if there are restrictions in Java, Kotlin will be fully backed up? I can think of that.
In other words, from the above flow, Kotlin will become the standard for Android, ** Android and iOS will become the standard for development with similar language specifications in the future? It is speculation that **.
And when that happens, ** the flow of unifying the app and backend in the same language from the perspective of engineer migration / learning within the organization will increase. I think that the. The reason is that we are entering an era where application development is the main focus, and that there are many merits of introducing Kotlin on the Web as described in 4.
This is the flow * of Kotlin taking the world from * App to the Web *.
Of course, Go is also popular for the back end, and the above is a complete reasoning, but Kotlin Conf is also held and Kotlin is showing excitement. Isn't it possible to think of the above world lines? I think.
Thank you for reading the article! If you find it helpful, please like it. M (_ _) m
Recommended Posts