Linked by Thom Holwerda on Tue 6th May 2008 15:15 UTC, submitted by Shlomi Fish
Features, Office "Which parameters make software applications high-quality? And which parameters or methods, while desirable, are not directly 'quality'?" This is the question the author of this article asks himself. Most of his 'parameters' make a lot of sense, but be aware that the article is about what makes an open source program high quality, and not programs in general. This important bit is stated in the one-sentence 'abstract'.
Permalink for comment 313533
To read all comments associated with this story, please click here.
bousozoku
Member since:
2006-01-23

Okay, so I'm joking. I always used emacs because I couldn't get anything done with vi because I couldn't remember the commands--ed was easier.

I also laughed at the 15 or so lines of output, thinking that there should have been some silent or quiet option, as a lot of small utilities used to have. I believe a lot of people I know just forgot to turn off the debug code and it made it into various utilities and no one ever bothered to fix them because they thought the extra output belonged there. Those same utilities probably never had any simple instructions for -? or -help or whatever other prompt.

Commercial software, whether it's Photoshop, an accounting system, or a development system, should just work and we shouldn't have to depend on workarounds. I still have nightmares about certain C/C++ compilers.

Even if the code is neat and clean on the inside, does that help on the outside? Does a liberal source code licence help? I hope so, but I have my doubts.

By the way, how do you quit vi?

Reply Score: 2