this post was submitted on 27 Sep 2023
677 points (97.6% liked)
Programmer Humor
32571 readers
411 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yea if that was where the issues happend that would be a great explanation.
But most issues in my experience (10 years in support fos business with about 25000 users) it's getting the data to the printer that is the issue. Drivers are unstable, the print spooler service randomly decides to just stop working and needing a restart etc etc.
And this is across lots of brands and different implementations (directly connected, network send to printer, central print server... You name it).
Somehow the complexity of this just makes it (apparently) impossible to make something that is just plain reliable. Personally I think it's a combination of several layers of tech needed to work that compounds the issues.
You have the software that need to encode the data in one of many ways a printer can receive data, you have the windows print spooler that apparently is a complete piece of crap held together with shoestring that gets to receive this data and then use the driver (often also a unstable piece of garbage) to send the data to the printer in a way the printer now understands.
Then you get to the part that actually mostly works unless something whent wrong with the encoding (like using the wrong driver) the printer gets a stream of data and does as it is told.
Yes you might get a paper jam or an unaligned page, but that is actually pretty rare in a professional, well serviced machine.