michaelothomas

4 ms·

1. 1.▲
   by michaelothomas 2y ago

   I mean, I thought it was a pretty good explanation. JavaScript plays fast and loose with types. Which means that when JIT compilers generate code for it, they have to make all sorts of conservative decisions. This makes generated code more
2. 2.▲
   by michaelothomas 2y ago

   Switching to WasmGC doesn't really change the equation here.
3. 3.▲
   by michaelothomas 2y ago

   The difference is primarily algorithmic. Java on WasmGC is about 2x slower than Java on the JVM. The remaining 50x is just Chrome's regex impl being awesome.
4. 4.▲
   by michaelothomas 2y ago

   The calculation engine was written in Java before Rust or Zig were invented.
5. 5.▲
   by michaelothomas 2y ago

   It was all of the above. We had a pretty awesome team of people working across the entire stack optimizing absolutely everything. The blog post only talks about the three optimizations that made the biggest difference.
6. 6.▲
   by michaelothomas 2y ago

   For larger applications things like method dispatch performance start to dominate and you land closer to 2x overall performance uplift.
7. 7.▲
   by michaelothomas 2y ago

   I don't know absolute values but Excel still has several advantages which make it faster: - Excel is written in C++ and compiled natively which will be a bit faster than Java running on the JVM. And Java running as WasmGC is about 2x s
8. 8.▲
   by michaelothomas 2y ago

   The WasmGC version is twice as fast as the JS version.