Just had a chance to watch the Keynote recording. ...

# random

[Gavin Ray]

Just had a chance to watch the Keynote recording.
Wanted to share my support, and some thoughts behind why I'm "betting big" on Kotlin's future:

JB seems to be the company hardest pursuing a "unified codebase" dream.
If you want to write an app, in a single language, that includes:
• Serverside API
• Native code (native binary, static/shared library)
• Unified UI that runs cross-platform (Web/Desktop/Mobile)
AFAIK, your options are:
• C++, Qt
• Java, Bck2Brwser, JavaFX, GraalVM (the Gluon stack)
• Scala, Scala.js, Scala Native or Graal
• Clojure, ClojureScript, GraalVM, some magic to get it running on Android/iOS like Gluon uses
• Kotlin, Compose (currently feels the most cohesive/integrated solution)
Jetbrains has the most to gain from "solving this" and also has arguably the most resources to throw at the problem.
I'm betting big on JB Skia bindings becoming the foundation for "Compose Everywhere", and Kotlin Native allowing me to drop C/C++ for when I need to integrate existing popular libs, or get dirty with a bit of low-level work.

The WASM backend was a logical leap, given that LLVM suports WASM/WASI as a target.
Many of the same API's can be re-used, IE binding to DOM <canvas> for drawing as well. (In this sense <canvas> in the WASM output becomes a rendering context like opengl)

Unless I'm dead wrong (which is entirely possible), seems like future is bright for Kotlin.
Going to be an exciting ride, better buckle up ;^)

[mcpiroman]

The WASM backend was a logical leap, given that LLVM suports WASM/WASI as a target.

Well, kotlin has had a WASM backend implemented via LLVM but now it's (going to be) deprecated and they're trying to assemble WASM natively. That's how I understand it at least.

[Gavin Ray]

The new WASM backend is a result of the refactoring around IR structure right?
This is what is allowing them to efficiently write new backends, some sort of better IR/commonized IR design?

[mcpiroman]

Yes, they just don't use LLVM along with IR for WASM, I think. But hey, today's the presentation about wasm backend so we may learn something there

[cedric]

Rust is curiously absent from your list @Gavin Ray and yet it meets pretty much all the same requirements as Kotlin, and maybe even a few more

[elect]

what's the Rust mobile UI?

[cedric]

Don't think there is one