Even after reading that, I still favor Ktor. Obviously if you’re doing a multiplatform client it’s much easier, but the current problem is with tooling and that will only improve so it’s all about how critical you are about your frontend app size. It’s not that critical for me

That was the goal of this test. Define what is essential for you. Not using Webpack also makes sense to benefit from client caching between different pages. But file distribution sizes may be critical in some context. That is why Kotlin needs to be on par or better than pure JS tools.

I also don’t know a lot about frontend development, Right now I’ve got a “big” js file packaged by webpack, but hopefully I’ll be able to offer all separate js files and make it work. If you just have to download 95% of the app size once even if I update my app daily, that’s cool for me. I’m not doing a landing page in Kotlin/JS

There is one problem: having (a) big(s) js file(s) means more time for the browser to parse it. We need an excellent DCE tool to remove ALL dead code and ease browser work. The distribution of applications depends on many use cases. In mine, I want fast loading because every page can be a landing page like this one: https://play.data2viz.io/pierre/sketches/dJbyoY/view/

I've never reach the point of even having Kotlin/JS. I am always confused with the configuration to get an output 😕

You can try by just getting my todokotlin project and launch

gradlew run

.