It may be a different answer than you expect...

A lot less developer time spent making sure the application fit in a tiny amount of memory.

Of course that sucks for you as a user when an application takes up 4+GB of memory for no reason (I'm looking at you Teams). But for the company that writes it, it is great. Compile and ship, no more weeks or months of trying to shave off every bit so you can fit this in 16MB of RAM, or on just a few floppies. You have a big customer that will sign a 10 million+ contract if you add feature X? Sorry, no way to make that work in under 105KB, which means we can't ship it.

Pretty much none. I used Word 97 well into the early 2000's. In the early 90's, my Amiga ran a decent word processor in 1 meg of RAM. Software expands to consume whatever resources are available: memory, disk, CPU, bandwidth...

It saves when the user wants to, not automatically without asking, saving even unintended accidential changes, and publishing them to others.

It runs locally, not rendering badly in the browser.

Saving to disk does not require navigation through 3 sub-menues.

Here's one -- cloud saves! Remember carrying floppies?

How about real time collaborative editing?

All the above cross platform?

C'mon now be realistic :).