<@U092308M7> you may tell that kotlinc-js is close...
# javascript
k
@orangy you may tell that kotlinc-js is closer to GWT, since both are sourcee-so-source compilers. However, I feel like TeaVM is much closer to GWT than kotlinc-js due to several reasons: 1. TeaVM is tightly integrated with "server-side" build tools like Maven (or, unofficially, Gradle). kotlinc-js tries to be more friendly to npm, WebPack, etc. 2. TeaVM is a closed-world compiler. It takes all available modules and tries to perform hardcore optimizations. kotlinc-js only sees one module and can't make any assumptions about the code. 3. TeaVM is intended for back-end developers who are used to Java ecosystem and want to reuse it as much as possible rather than learning completely new JavaScript ecosystem. kotlinc-js forces you to learn JavaScript ecosystem. 4. TeaVM has its own framework which follows Kotlin/Java programming idioms, while kotlinc-js tries to integrate with React.js, which follows JavaScript idioms.