Ted Leung on the air
Ted Leung on the air: Open Source, Java, Python, and ...
Ted Leung on the air: Open Source, Java, Python, and ...
Mon, 01 Mar 2004
It happened to me too
Lots of people are referencing ESR's tale of woe regarding the CUPS UI. I had a very similar experience with CUPS. I was trying to get my HP LaserJet 2100DTN to print in duplex mode. It was decidedly non-trivial to figure out what needed to be done to get it to work. It was so arcane that I even had to write it down.
Maybe it'll make the next edition of my Macintosh Tips and Trick page. Oh, that's right, I forgot to mention that little fact. This happened on Mac OS X, which is supposed to the shining example of how to take open source software and make it usable. The fact the even Apple's reknowned engineering team had trouble making this easy signals a real problem. Most of the open source community has less experience making things easy than the folks at Apple.
I can't count the number of hours that I've wasted over arcane setups for applications on either Windows or Linux/UNIX. I've lost count of the number of my friends who think that they are stupid because they can't get a computer to work properly. It's a disgrace. Computer software may have saved people an enormous amount of work and unleashed a tremendous amount of productivity, but its also been responsible for wasting an incredible amount of people's time on problems that should never have been there in the first place. If the "open source community" really wants to make an impact, then we are going to need to learn how to make software easy to use. This is true for every interface in software, user interfaces, and programming API's. Life is too short to waste time on stuff like this.
[23:38] |
[computers/open_source] |
# |
TB |
F |
G |
5 Comments |
Both you and ESR are way into edge case land.. this is Apple's first year of CUPS, too.
Is it a real problem that Apple and the CUPS team neglected to make it easy to configure a relatively obscure print feature that most people don't use? For a printer that uses a proprietary protocol? I don't think so.
If you had purchased a PostScript compatible printer from a manufacturer that provides PPD files then it should work rather easily (out of the box easily). Open standards are good.
I think people need to stop complaining about open source and start donating and/or submitting patches. I do both (and then I complain ;). I bet you didn't even file a bug on Apple's radar.. I'm told they actually do read it, and I have received (late) responses for most of the bugs and feature requests I've filed. Even if you're sure it's common, it's still worth reporting it because issues they see a lot are prioritized accordingly.
Posted by Bob Ippolito at Tue Mar 2 01:04:22 2004
Is it a real problem that Apple and the CUPS team neglected to make it easy to configure a relatively obscure print feature that most people don't use? For a printer that uses a proprietary protocol? I don't think so.
If you had purchased a PostScript compatible printer from a manufacturer that provides PPD files then it should work rather easily (out of the box easily). Open standards are good.
I think people need to stop complaining about open source and start donating and/or submitting patches. I do both (and then I complain ;). I bet you didn't even file a bug on Apple's radar.. I'm told they actually do read it, and I have received (late) responses for most of the bugs and feature requests I've filed. Even if you're sure it's common, it's still worth reporting it because issues they see a lot are prioritized accordingly.
Posted by Bob Ippolito at Tue Mar 2 01:04:22 2004
er, second year of cups.. but still, there's a lot of printers out there.
Posted by Bob Ippolito at Tue Mar 2 01:05:30 2004
Posted by Bob Ippolito at Tue Mar 2 01:05:30 2004
Its slightly perverse that the age old Apple Mac Classic Chooser was such a simple and easy way to pick and use a printer.
OS X Printing seems like a step backwards in this respect - long term I imagine Apple & the CUPS team will nail these usability issues.
Hopefully things like Rondezvous and Universal Plug & Play will make this type of thing much much easier.
Raj.
Posted by Raj at Tue Mar 2 07:01:26 2004
OS X Printing seems like a step backwards in this respect - long term I imagine Apple & the CUPS team will nail these usability issues.
Hopefully things like Rondezvous and Universal Plug & Play will make this type of thing much much easier.
Raj.
Posted by Raj at Tue Mar 2 07:01:26 2004
The printer is a 2200 which is my typo. The 2200 is postscript L2 compatible, and there are/were PPD's and it was still a pain. It was actually easier on Windows.
As far as reporting a bug, sure, I could report a bug, but all the friends and family that I've spent time helping over the years would definitely not be reporting a bug.
Building systems for non-geeks is hard, and there's still a long way to go -- which was really the point of my post, not so much as a rip on CUPS, since you can find similar issues with lots of other projects.
Posted by Ted Leung at Tue Mar 2 17:09:58 2004
As far as reporting a bug, sure, I could report a bug, but all the friends and family that I've spent time helping over the years would definitely not be reporting a bug.
Building systems for non-geeks is hard, and there's still a long way to go -- which was really the point of my post, not so much as a rip on CUPS, since you can find similar issues with lots of other projects.
Posted by Ted Leung at Tue Mar 2 17:09:58 2004
If nobody reports a bug, it won't get fixed. Which means you'll inevitably be wasting more of your time again on the same (or similar) issue sometime in the future.
If a non-geek calls tech support (or.. you), the tech support staff (or.. you) might end up filing a bug about it.
Posted by Bob Ippolito at Tue Mar 2 19:47:33 2004
If a non-geek calls tech support (or.. you), the tech support staff (or.. you) might end up filing a bug about it.
Posted by Bob Ippolito at Tue Mar 2 19:47:33 2004
You can subscribe to an RSS feed of the comments for this blog:
Add a comment here:
You can use some HTML tags in the comment text:
To insert a URI, just type it -- no need to write an anchor tag.
Allowable html tags are:
You can also use some Wiki style:
URI => [uri title]
<em> => _emphasized text_
<b> => *bold text*
Ordered list => consecutive lines starting spaces and an asterisk
To insert a URI, just type it -- no need to write an anchor tag.
Allowable html tags are:
<a href>
, <em>
, <i>
, <b>
, <blockquote>
, <br/>
, <p>
, <code>
, <pre>
, <cite>
, <sub>
and <sup>
.You can also use some Wiki style:
URI => [uri title]
<em> => _emphasized text_
<b> => *bold text*
Ordered list => consecutive lines starting spaces and an asterisk