3 ms·
Agreed, once the final missing pieces are in place (mainly garbage collection at this point) javascript will be an opt in kind of thing rather than the only ava
by jillesvangurp 8y ago
Agreed, once the final missing pieces are in place (mainly garbage collection at this point) javascript will be an opt in kind of thing rather than the only available choice.
Personally, I might get my hands dirty with Kotlin on the frontend. I'm using it on the backend currently so the transition should be relatively smooth for me and I have some crappy JS code that I would love to get rid of at the earliest convenient moment. I imagine there are also a lot of Android developers that might be willing to work on Kotlin based web apps that like me would prefer to not deal with Javascript.
I imagine short term things will be a bit rough as tooling and frameworks are still evolving. But as that improves, there will be a very sharp increase in the amount of non JS code running in browsers. Currently the big milestones for Kotlin would be the 1.0 release of the native compiler (0.8 is the latest, I believe), related work on WASM support, and the finalization of things like garbage collection in WASM. Looks like that should all be happening over the next 6-12 months.