Linked by Thom Holwerda on Sat 21st Jul 2012 23:06 UTC
Permalink for comment 528015
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
More News »
Sponsored Links



Member since:
2007-11-23
Hello again,
As I already said I do realize I generalized the problem. However, the real issue remains unsolved: we have NO access to proprietary code. Nobody can see if it's really good, or if it's just a badly written code.
How would you measure code quality if you don't have an access to the source? DO you want to judge upon such factors as "stability"? Well, this can be accomplished by using dirty hacks, tricks inside the code. Everything runs just fine, but the code is NOT good, which is something you should already know as an OpenBSD user [I am an OpenBSD user and OpenBSD [3rd party] software developer myself, so I thought we should share the same point here].
As of the other things you mentioned: I do not say that every proprietary code developer writes "crap". I just say we have no ways to see what's the real value of proprietary code.
Bye and sorry it it makes you angry. That was not the point. It was and is all about access, knowledge and quality.