One of the reasons I'm hesitant to use KVision ins...

# kvision

[spierce7]

One of the reasons I'm hesitant to use KVision instead of something like react is just how many nice libraries that React has for UI components etc.

I'm curious if there is a solution to this, i.e. if KVision plays nicely with other UI frameworks.

[Robert Jaros]

You can use React UI components with KVision as well. But you need to write your own Kotlin language bindings for them.

[spierce7]

your own Kotlin language bindings for them.

By this you mean external declarations?

[Robert Jaros]

Yes

[spierce7]

This is expected. Dukat has fallen woefully short. 😞

[Robert Jaros]

https://kvision.gitbook.io/kvision-guide/4.-integrating-with-javascript-libraries/using-react-components

[Robert Jaros]

You can even put kvision component into react component embedded in kvision app ;)

[spierce7]

that might be helpful.

What can we expect with the KVision bundle sizes?

[Robert Jaros]

https://kvision.gitbook.io/kvision-guide/faq#what-is-the-size-of-a-typical-application

[spierce7]

Is there any approach recommended for lazy loading?

[Robert Jaros]

Unfortunately Kotlin/JS doesn't support lazy loading.

[spierce7]

I don't know anything about lazy loading anyways 😛

[Robert Jaros]

When using Kotin/JS for the UI of your web application you have more or less three choices:
1. build your app with basic html - no external declarations but also no advanced components
2. write externals, be happy with components, maintain the externals, update packages, fix bugs, update, fix, update, fix ... 😉
3. use KVision 🙂

[spierce7]

I'm curious how KVision will compare with Compose JS Canvas

[spierce7]

I get TornadoFX vibes while looking at the KVision samples

[spierce7]

The KVision showcase performs really well.

The password forms don't play nicely with my password manager. I'm assuming that's because the field is being changed reactively behind the scenes.