[Rinzler89]

Canon doesn't develop MacOS. They advertise support for the version of MAcOS that existed when they launched the printer. If MacOS decides to break compatibility over time, it's not their fault. If they're not selling the printer today, they can't also provide up to date support for the OS of today. It's up to the OS developer to ensure a stable API for printers.

[acdha]

“Break compatibility” can cover a wide range of things, however, and that’s not always so clear cut. For example, if they were relying on lax permissions or a private interface then it’s a question of how much effort the OS vendor should spend on something they never promised would work.

[paulmd]

Imagine the IP camera vendors saying this :skull:

“What can you possibly be complaining about!? It was secure when we released it! Maybe you should just buy a new one with less vulnerabilities!”

EU isn’t wrong that people have an intuitive sense that appliances like printers should have a worthwhile lifecycle and for some classes of devices this lifecycle should be quite long. 10 years really isn’t unreasonable.

Also, just like everyone has to support usb-c charging regardless of whatever other proprietary alternative they design… vendors should have to support a couple generic standards (postscript/Ghostscript and CUPS) that relieve a lot of the ongoing maintenance. There are very few/no valid reasons you couldn’t implement cups/postscript if you really want.