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 313148
To read all comments associated with this story, please click here.
jabbotts
Member since:
2007-09-06

"
Only in the open source world, where it seems that people are used to being stuck with a buttload of alpha/beta-quality software on Sourceforge does this make absolutely any sense.
"

yeah, because software from outside the FOSS world has never been known to be beta quality at time of purchase has it.

Please, the FOSS types are nuts because they accept a few bugs as a tradeoff for more flexible software without mysteries. The non-FOSS types are nuts because they accept steaming turd nutty quality software (How's Vista doing these days?) like it was handed down on two stones. All of it is human written software so it's all buggy crap; The FOSS types just discuss it openly instead of hiding behind closed doors fo fear of marketing image.

I do like your list of attributes though. portable, modular, customizable configuration.. I have to reread the article but I think your much closer to what makes software of high quality though I'd add peer reviewable source code as a bonus (but not a deal breaker if code quality doesn't suffer).

Edited 2008-05-06 18:36 UTC

Reply Parent Score: 2