Linked by Thom Holwerda on Sat 21st Jul 2012 23:06 UTC
In the News Okay, so this is entirely new to me. Sparrow is was an email client for Mac OS X and iOS (and Windows), which brought a decent Gmail experience to these platforms - as opposed to Apple's own not-so-good Gmail support and Google's Gmail iOS application which, well, is just a webpage. Google has now acquired Sparrow, and basically all hell has broken loose, to the point of Rian van der Merwe writing that 'we' lost "faith in a philosophy that we thought was a sustainable way to ensure a healthy future for independent software development, where most innovation happens".
Thread beginning with comment 528015
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by sicofante
by marcp on Tue 24th Jul 2012 09:07 UTC in reply to "RE[4]: Comment by sicofante"
marcp
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.

Reply Parent Score: 2

RE[6]: Comment by sicofante
by lucas_maximus on Tue 24th Jul 2012 10:42 in reply to "RE[5]: Comment by sicofante"
lucas_maximus Member since:
2009-08-18

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.[/quote]

TBH all that matters to a user that it works as advertised aka to requirements. The development team is the only people that should be worried about code quality as bad code costs the business development time.

It is also rather trivial to see how a program works (profiling, tools such as wireshack, to how a program is working behind the scenes).

[q]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.


I don't have to measure code quality, I am the user not the development team.

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].


I might be a user but I do not believe in an extreme philosophy that all code my be open and one cannot judge quality unless we can see the complete source code.

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.


You said it was crap code and they will be sued and a lot of other nonsense.

Bye and sorry it it makes you angry. That was not the point. It was and is all about access, knowledge and quality.


You are taking things to an extreme, it doesn't help anyone. Sorry what you have is a belief.

I will keep on saying it, open source isn't magical bullet. It works for some projects and companies ... others it would kill their business model.

Reply Parent Score: 2