- 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.
推薦閱讀
- Dynamics 365 for Finance and Operations Development Cookbook(Fourth Edition)
- 數據科學實戰手冊(R+Python)
- Web前端開發技術:HTML、CSS、JavaScript(第3版)
- TypeScript入門與實戰
- Twilio Best Practices
- BeagleBone Media Center
- Swift 3 New Features
- Modular Programming in Java 9
- 算法訓練營:提高篇(全彩版)
- Hands-On Swift 5 Microservices Development
- Visual Basic程序設計實驗指導(第二版)
- 區塊鏈項目開發指南
- 現代C:概念剖析和編程實踐
- Microsoft HoloLens By Example
- Learning Shiny