Not when you're working on proprietary/confidential/classified information.
>But many/most Spreadsheets can be done in Libreoffice, or code or no/low code alternatives.
Not when you're working on spreadsheets that you need to send to organizations that heavily rely on MS Office.
Why not? The WASM approach the OP is suggesting works entirely locally, the web is simply pushing client code to your browser.
Because "the web is simply pushing client code to your browser". Untrusted code. Which may violate the confidentiality of you document. I still don't get it why companies which deal with "confidential information" are very happy to put those documents in the cloud. But ... it is their data and they decide what to do with it.
Is the WASM "untrusted"? Sure, I guess, all code you haven't written yourself is "untrusted" by default. Why would a native application shipped via CD or download be any more "trusted"?
Oh and it's soooo slow :(
File comparison, hard applications, legacy code, can be compiled to WASM and run quite well in the browser. The pieces are in place to do it, they just need polishing and tuning to make it ubiquitous. Even Excel could be compiled like this but again MS wants to own you and pin you over a barrel while extracting everything they can from you, so Excel won't be available. But many/most Spreadsheets can be done in Libreoffice, or code or no/low code alternatives.