is `Compose-Web` (assuming no internet access) as fast as `Compose-Android` and `Compose-Desktop` ?

# compose-web

[Koneko Toujou]

is Compose-Web (assuming no internet access) as fast as Compose-Android and Compose-Desktop ?

[hfhbd]

Compose Web produces a regular js file, you don't need internet access. Also, what do you mean by fast? The default stable version uses the HTML DOM API without a virtual dom like react and without a lazy table.

[Arjan van Wieringen]

It’s slower. But that’s to be expected. Its the DOM that is modified and not a graphics accelerated Skia draw call

[Arjan van Wieringen]

Still very performant though

[Koneko Toujou]

like, suitible for high performance graphical applications

[Koneko Toujou]

eg, stuff that Compose-Android/Desktop should easily be able to handle in terms of graphics but Compose-Web cant handle very well

[Oleksandr Karpovich [JB]]

https://github.com/OliverO2/compose-counting-grid#findings - here @Oliver.O made a comparison you may be interested in.

[Koneko Toujou]

interesting :)

[Koneko Toujou]

hmm

This application does not simulate any real-world scenario as it uses a very simple layout with fixed-size cells.
    Compose for Web on Canvas is at an experimental stage. This application uses funky tricks to fit the canvas to its content size.

[Koneko Toujou]

Currently, it appears that the entire (window) canvas is redrawn on every frame. Once JetBrains/skiko#53 is fixed and only updated parts are redrawn, expect significant performance increases.

what does this apply to?

[hfhbd]

Compose for Web on Canvas does not use the (stable) DOM API but instead creates the UI directly on canvas elements which is experimental. But, as you can see, the whole window is redrawn every time and not changed elements only.