I’m a big fan of Kotlin, I know how well it performs inside the browser but I also feel the current limitations for a real adoption in the browser. This is why I want to recap the missing features and would like to know if their are going to be resolved and when (approximatively).
Aligning Kotlin/JS development with current frontend workflow
Nowadays, frontend development is quite effective. The main point of it is the very efficient loop between modifying code and seeing the result. With webpack-dev-server, live/hot reload, the developper modify its code, js / typescript or Sass / Less files and have a near immediate view of its modifications in the browser. The build chain detects modifications of the code, do the compilation/transpilation work and reload it in the browser.
We should have that with Kotlin/JS. Now that Kotlin/JS incremental compilation is here, we should have this quick modification/compilation phase integrated in webpack development workflow and tools. And this workflow should be documented.
Efficient Dead Code Elimination and code splitting
The current DCE is a good first step. We can have relatively small minified/zipped Kotlin/JS files.
However, the DCE could go really further. It currently keeps a lot of unused code. Also, it’s now common to do frontend code splitting. It should be possible with Kotlin/JS development and compatilbe with DCE.
- lib/kotlin-std.js // DCE applied but containing all code used by modules page1 and page2.
Can Kotlin/JS jetbrains team give a feedback on the current and future status on these points?