if you really want to strike a blow to Google you gotta stop vilifying printers because the single biggest use of Google docs in aggregate is sending office documents to people when both parties are unwilling to use a printer, scanner, or fax.

and, why? a fax has a certain gravitas.

a fax is a threat.

fun fact regarding printers and blows against google:

when google discontinued the Cloud Print API and they began turning the service off, they noticed a large, sustained increase in traffic to the defunct api

printers with Cloud Print would normally reach out to the google servers to check connectivity, transmit metrics, etc

a huge number of these printers operated under the assumption that if the Cloud Print API was down, it was probably an intermittent network issue, and that it should try again after a short time without getting a reply

the timeout periods were short, static intervals (as opposed to like exponential backoff) and would retry indefinitely

by shutting down the cloud print API, printers globally began impatiently and relentlessly pinging the api. and the google load balancers had to read every request and decide to drop it.

google caused a huge, costly DDOS attack on themselves. People don't often update the software on their printers, and getting vendors to patch this would be time-consuming and difficult. The only end in sight was when every printer was eventually unplugged and thrown in the garbage

Quickly, a stub service was put in place to respond to connectivity and update checks with a polite acknowledgment. The time between periodic connectivity checks was far longer than the time between reties for failed requests. It was decided that it would be much cheaper to run the stub indefinitely than to bear the brunt of eager printers aching for acknowledgement from the cloud print api

the year is 2033. no one in Alphabet knows why there's a $1.7M/yr google cloud instance bill with a "DO NOT UNPLUG" sticky note on the front