Linked by Thom Holwerda on Thu 8th Nov 2012 20:54 UTC, submitted by Elv13
Gnome "Theme development is a tedious and difficult task, and for the GTK devs to be so careless in breaking their API at every turn disrespects the many hours people put into making themes for it. [...] I was given to believe that this breakage stems from a Microsoft-like climate of preventing users from customizing their systems, and deliberately breaking the work of others so that your 'brand' is the best. Anytime I hear the word 'brand' being used in Linux, I know something valuable is being poisoned." I find the tone of this one a bit too harsh and overly negative at times, but his point still stands.
Thread beginning with comment 541594
To read all comments associated with this story, please click here.
lucas_maximus
Member since:
2009-08-18
renox Member since:
2005-07-06

And quite a few people found his post of a very low quality..

Reply Parent Score: 4

lucas_maximus Member since:
2009-08-18

And who was that? Mainly the people he was criticising.

I haven't seen one post rebuttal yet that actually invalidated any of what he said.

Edited 2012-11-09 13:11 UTC

Reply Parent Score: 1

segedunum Member since:
2005-07-06

Miguel's post was nonsense and more than a bit ironic, because as Alan Cox pointed out, he started and caused many of the fundamental problems. Much of the software he was at least partly responsible for coming up with was of such poor quality that it went through the very API churn and develop dissilusionment that he is talking about.

Reply Parent Score: 3

lucas_maximus Member since:
2009-08-18

No It wasn't.

It doesn't matter even if he was part of the cause of the API churn.

He acknowledged:

* It exists
* He was partly to blame.

It is irrelevant he might have been part of it or even started it. Hindsight is 20/20 as they say. He was a lot younger then and probably didn't know what he knows now.

Edited 2012-11-10 09:09 UTC

Reply Parent Score: 2