- Kotlin Blueprints
- Ashish Belagali Hardik Trivedi Akshay Chordiya
- 231字
- 2021-07-02 21:50:10
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.
推薦閱讀
- JBoss Weld CDI for Java Platform
- Unreal Engine Physics Essentials
- Learn Type:Driven Development
- LabVIEW Graphical Programming Cookbook
- Android Development with Kotlin
- Unity 2020 Mobile Game Development
- Linux環境編程:從應用到內核
- 精通Python自然語言處理
- Mastering Drupal 8 Views
- Nginx實戰:基于Lua語言的配置、開發與架構詳解
- Learning FuelPHP for Effective PHP Development
- Test-Driven JavaScript Development
- 關系數據庫與SQL Server 2012(第3版)
- 編程的原則:改善代碼質量的101個方法
- Learning Ionic(Second Edition)