A friend of mine used to work on a product that was essentially a printer driver.
The problems include (1) QA, (2) reverse engineering the communication protocol, and (3) support.
#1 and #3 are chronic issues in the OSS world. They're also a problem because there are a ton of printers out there, and getting one to develop/test against eventually becomes an expense and space problem.
And, printers are cheap. There's no real financial incentive to do it.
As an aside, I talked to some guy at Chase years ago, and all he wanted was some way to manage all the printers Chase had. That was it. It was like his personal nightmare. It was literally an impossible task, especially since some unknown percentage of them were no longer manufacturer supported...and many didn't have a manufacturer anymore.
This is why financials want you to go all-digital - so they can dump these behemoth printers that cost a fortune to maintain.
The problems include (1) QA, (2) reverse engineering the communication protocol, and (3) support.
#1 and #3 are chronic issues in the OSS world. They're also a problem because there are a ton of printers out there, and getting one to develop/test against eventually becomes an expense and space problem.
And, printers are cheap. There's no real financial incentive to do it.
As an aside, I talked to some guy at Chase years ago, and all he wanted was some way to manage all the printers Chase had. That was it. It was like his personal nightmare. It was literally an impossible task, especially since some unknown percentage of them were no longer manufacturer supported...and many didn't have a manufacturer anymore.
This is why financials want you to go all-digital - so they can dump these behemoth printers that cost a fortune to maintain.