I get their reasoning and I admire the courage. But IMO they should have went with Rust -- smaller WASM binaries and even better memory footprint. And they sai

I get their reasoning and I admire the courage. But IMO they should have went with Rust -- smaller WASM binaries and even better memory footprint. And they said these were concerns. So IMO they didn't go far enough. But it's also completely understandable. They already had a Golang codebase. So it was either go all in in the JS/TS ecosystem or all in in the Golang ecosystem. They made the right choice but again, they could have went even further and kill all birds with one stone. A heavy and quite time-consuming stone, granted.