A big aspect of this is data collection. Microsoft office has tons of features that could easily be local buy that it wants to be "connected services" that are subject to their own TOS so they can steal your data. Based on the lag, it seems like all spell and grammar checks go through some server somewhere, almost certainly with the primary goal of scraping as much info as they can from what you're doing. Online first is all about data harvesting, much less so ease of operation and certainty not customer experience.
I think the acronym used to represent the phrase "The F*ing Article", and then, for a softer touch, people changed F to represent 'Fine'.
which itself is from RTFM (manual), which was the catch-cry of early 90s irc and usenet tech newsgroups.
> 1. Users are offline; experiencing latency issues or are in unreliable network conditions.
> 2. Fetching the data over the network will be slower than fetching it from a local source.
> 3. The app users should be informed about the low network conditions but it shouldn’t be a hindrance to their objective.
> 4. Users’ network and battery status are taken into account, and thus only the data that has changed since the last synchronization should be synced.