Don’t believe I can say the same for Ethernet. Let alone WiFi, God help us.
Not to speak of LPR (which does have the advantage of not having to set up anything printer-specific on the client, but it is a pain to set up on the server).
For wifi all you need is to enter the wifi password.
So near and yet so far because it required an Android app to configure the wifi password, despite the printer having a 2.5" display and a simple keyboard. But apart from the Android app the printer just worked out of the box with CUPS and SANE.
Actually the whole of printing is still a pain, my printer (on wifi, because it has wifi but no ethernet despite being plenty big enough for an ethernet port and thus having no reasonable excuse not to have one) randomly decides not to exist, or Windows decides it's perpetually stuck, or that a job has not finished, or the Linux box stops being able to get any kind of coherent reply from it, or my Android phone starts printing everything all fuzzy.
The latter might be the phone's fault, I haven't quite figured that one out yet.
I daren't get another one because I can't trust that any other printer will behave, but this is a Hewlett-Packard. You would think HP would have figured out how to make a printer that actually WORKS by now.
They were a lot easier when they just plugged into the parallel port. Okay so you spent a couple of hours trying to get the right drivers in place, but once you did it generally just worked and kept on working. The latter seems to be something they're incapable of delivering these days.
I can't see why someone thinks it's a good idea to drop the resolution when printing from a phone, but maybe it's because phones running Android 2.2 might run out of memory.
And now that KRACK is here, you can only wonder who gets a carbon copy.