Apart from the obvious compatibility disaster, what kind of skeletons does Microsoft have in their printing system that the choice of C library creates those compatibility issues in the first place?
I don’t know if this C library helps mitigate this but Print Spooler is not “it just works” either.
> will intentionally fail to print to remote print servers
Why would a more secure local print driver refuse to talk to _remote_ print servers? What is so untrustable about what comes over the wire, and if it is, how can they trust the print server is or is not one is claims to be and can be talked to?
Not only that but it seemed every time they fixed a vulnerability some piece of functionality broke.