官术网_书友最值得收藏!

Go native strategy

The Kotlin developers figured that the same strategy that is used on the JVM platform could be used on other platforms too. Consider the following illustration:

On no platform does Kotlin disrupt the platform's existing technology:

  • The JVM works with the Java bytecode and Kotlin gives an alternative to Java to generate the same bytecode (By no means is Kotlin the first alternative as there are already 200+ languages that work with JVM, but it is the most elegant one for all the reasons that we have seen previously).
  • On modern browsers where JavaScript is the de facto standard, Kotlin can work by transpiling to JavaScript. Again, this means that Kotlin is friendly with existing browsers without making any special effort.
  • On the Node.js platform where JavaScript is used on the server side, your Kotlin code transpiles into JavaScript, and hence there are no changes needed in the Node.js framework for Kotlin to run.
  • In a similar way, Kotlin/Native plans to work with other technologies in a native way. As we will see in Chapter 7, CSV Reader in Kotlin Native, Kotlin/Native will be used to generate Native code.

Since the platform's technology is not disrupted, there are zero changes needed at the platform level to adopt Kotlin. Kotlin's compatibility with a given platform can be taken for granted from day one. This eliminates a big business risk.

主站蜘蛛池模板: 洛浦县| 万盛区| 汾西县| 宁波市| 收藏| 玉溪市| 赤壁市| 美姑县| 通河县| 泸水县| 兴国县| 恭城| 江津市| 呈贡县| 休宁县| 利津县| 阿坝| 寻乌县| 永城市| 墨脱县| 察哈| 嘉祥县| 临清市| 浦县| 台中县| 新疆| 马公市| 友谊县| 武城县| 新密市| 印江| 桃园市| 剑川县| 临城县| 方山县| 民和| 韩城市| 杂多县| 临夏县| 马龙县| 巨野县|