The composable have a ID that I can get? and three's any callback that I can set when my composable is removed from the SlotTable?

ID: not really. what is it you’re trying to do? callback: Yes. you could use

onDispose

for this

I want to try make compose work in Kotlin JS

neat. what causes the id requirement for that?

I read that React uses keys, but thinking better now, I could use remember to cache the exacly element. The truth is that I have zero background in Frontend but I see that the Compose could be great three too and I want a study more the under hoods of compose in this carnival.

if you really want to go down this path, i’d be happy to chat and brainstorm a little bit more about what might be involved. i don’t think you’d need anything special with keys, based on how our runtime works. My guess is if you got compose runtime to compile to kotlin JS, you’d already be very close. After that, the primary thing would be to build a scheduler and a

Composer

subclass that knew how to target DOM nodes. Then you’d want to figure out the right way to expose those DOM nodes to the type system (there’d be a couple of options here i think)