News for hackers. Stuff that matters.

A comment on Why Google Sheets ported its calculation worker from JavaScript to WasmGC. Parent comment

Re:Why Google Sheets ported its calculation worker from Java... by eknkc on Thursday June 27, 2024 @11:42AM (#40811699)
Likely because they are compiling Java with WasmGC extensions and stuff. If you try C, Rust, Zig etc they tend to run extremely fast in WASM.

Go also has a WASM target which runs pretty slow compared to its native binaries. GC extensions might help but as far as I can remember, Go's memory model does not fit the WasmGC so it might never be implemented.

[ Parent | on HN ]
Re:Why Google Sheets ported its calculation worker from Java... by tracker1 on Thursday June 27, 2024 @12:10PM (#40812088)
I'm somewhat curious why they even chose Java over Rust or Zig, considering the spreadsheet data paths should be relatively straight forward even with a lot of clone() activity.
[ Parent | on HN ]
Re:Why Google Sheets ported its calculation worker from Java... by michaelothomas on Thursday June 27, 2024 @12:19PM (#40812209)
The calculation engine was written in Java before Rust or Zig were invented.
[ Parent | on HN ]
Re:Why Google Sheets ported its calculation worker from Java... by tracker1 on Thursday June 27, 2024 @01:15PM (#40812767)
Gotcha, I made the mistaken assumption this was a rewrite.
[ Parent | on HN ]