I can understand the Kotlin/Wasm use case for the browser, but somehow I fail to see the use case for NodeJS. Wouldn't it be better, also from an ecosystem perspective, to just run Kotlin/JVM on a, well, JVM container? Is this all about hot reload / deployment? I'd be interested in the performance differences between the two.
I think in 2023 you'd want to use JVM, but this is a JVM competitor long-term. But now, especially using Kotlin it currently doesn't make much sense, Kotlin Multiplatform's ecosystem doesn't hold a candle to JVM's.
I think the good part is the ability to deploy to nodejs/deno isolates on the many providers which allows to have serverless services with low (50-80ms) startup time Now we can write them on many languages and deploy to same infra
I think this video is a good pointer to be aware that Kotlin now supports WASM and great that it opens these possibilities. I was expecting a bit more in-depth explanation of the where, when, and how's of this though.
you showed how to invoke Kotlin from JS, but what about the other way? I'd ideally like to not use JS and use a more structure appraoch like kotlin, can I embed Kotlin into my HTML?
Because you can't consistently render things with the dom. The Dom is designed to change based on browser settings, OS settings, etc. Shipping skia ensures a consistent experience across platforms
@@kyay10 but browser settings exist for a reason. If someone sets their font size to something large, they probably have eyesight issues and can't read small fonts. Consistent experience does not mean better experience
@@dominikotocan1348 you can still support those settings. The point is to have pixel-perfect consistent rendering without having differing bugs between websites.
Blazingly fast!
Really excited for this! Thanks to the Kotlin team!
Multiplatform looks awesome!
If you have any questions about Kotlin/Wasm or Wasm GC, don't hesitate to ask below.
whats the difference between this and the kobweb framework?
I can understand the Kotlin/Wasm use case for the browser, but somehow I fail to see the use case for NodeJS. Wouldn't it be better, also from an ecosystem perspective, to just run Kotlin/JVM on a, well, JVM container? Is this all about hot reload / deployment? I'd be interested in the performance differences between the two.
I think in 2023 you'd want to use JVM, but this is a JVM competitor long-term. But now, especially using Kotlin it currently doesn't make much sense, Kotlin Multiplatform's ecosystem doesn't hold a candle to JVM's.
I think the good part is the ability to deploy to nodejs/deno isolates on the many providers which allows to have serverless services with low (50-80ms) startup time
Now we can write them on many languages and deploy to same infra
I think this video is a good pointer to be aware that Kotlin now supports WASM and great that it opens these possibilities. I was expecting a bit more in-depth explanation of the where, when, and how's of this though.
I really want compose have hot reload before the next move :)
that would be so cool 😁
I thought that compose already has it...
@@nem1st this is not hot reload. Just preview.
Kotlin compiler is very slow, I think it might take a _really_ long time to add hot reload
which http client is supported in wasm ?
Thank you for this great overview! 🙂
you showed how to invoke Kotlin from JS, but what about the other way? I'd ideally like to not use JS and use a more structure appraoch like kotlin, can I embed Kotlin into my HTML?
Eagerly awaiting
Great stuff.. 🎉
Does compose web use this technology to work?
Compose-web: yes. Compose-html (what used to be called compose-web): no.
🎉 Kotlin ❤
I am getting mad becas there is no Ktor support
I thought WASM is Watcom Assembler
It was a great example, but I was expecting a real example of using wasm with a React project.
Cool tech
This will be great to use in combination with wasm containers!
Goodbye graalvm.
I get runtime errors even when running the basic example. Should we not be using the main branch?
❤
Idk about that web thing. Why ship skia if you habe the dom. Just render to the dom. I think you did that before with compose for web
Because you can't consistently render things with the dom. The Dom is designed to change based on browser settings, OS settings, etc. Shipping skia ensures a consistent experience across platforms
@@kyay10 but browser settings exist for a reason. If someone sets their font size to something large, they probably have eyesight issues and can't read small fonts. Consistent experience does not mean better experience
@@dominikotocan1348 you can still support those settings. The point is to have pixel-perfect consistent rendering without having differing bugs between websites.
16:20 dedciated => dedicated
I cannot be the only one triggered by that white paint splash on the red cabinet behind seb.
You are not the only one who saw that white paint splash. It was actually the first thing I noticed in this video. :)
It a reflection of the ceiling light
@@gi1dor or of the light box to get better lighting. That makes sense. 😅
More shit!😂