What optimizations can are still yet to be done fo...

# webassembly

[spierce7]

What optimizations can are still yet to be done for the JetBrains team for WASM? Is tree shaking in yet?

[Svyatoslav Kuzmich [JB]]

Tree shaking is in, and there’s probably some room for improvement. We have some ideas for other things, but not a concrete list of pending optimizations. We’ll evaluate the priority based on real app benchmarks and figure out the the best place for them to be done. It could be a library code, binaryen, Wasm engine, or Kotlin compiler.

[spierce7]

Any idea how the current size compares to the same application in JS?

[Oliver.O]

See remarks about sizes in the "Changes" section here: https://github.com/OliverO2/compose-counting-grid

[Robert Jaros]

@spierce7 a hello world app written in Kilua compiled with K/JS - 422KB, compiled with K/Wasm - 497KB (.wasm) + 17KB (.js).

[Robert Jaros]

You can checkout and play yourself: https://github.com/rjaros/kilua

[bashor]

@Robert Jaros I guess it’s uncompressed size, right? Could you please check size after brotli --best ?

[Robert Jaros]

Can I use it from gradle somehow ?

[Robert Jaros]

Or you just want me to run the command on the wasm file?

[Robert Jaros]

It's 111KB

[Robert Jaros]

To stay on topic, JS is still a few bytes ahead with 94KB.