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 541624
To view parent comment, click here.
To read all comments associated with this story, please click here.
lucas_maximus
Member since:
2009-08-18

Well you suck at reading comprehension.

He was talking about the attitude that is was okay to break APIs, is prevalent because of Linus. While people could argue about whether this is true or not it really doesn't matter whos fault it is.

Breaking APIs is the problem with no path to follow while transitioning. Which is what the blog post is about.

Edited 2012-11-09 14:19 UTC

Reply Parent Score: 0

renox Member since:
2005-07-06

Breaking APIs is the problem with no path to follow while transitioning. Which is what the blog post is about.


Yes, and one cannot help but notice that when he was leading a major Linux project he didn't do anything special about this point..

Reply Parent Score: 3

lucas_maximus Member since:
2009-08-18

He does say "we" when referring to those that were guilty of it.

Edited 2012-11-09 15:19 UTC

Reply Parent Score: 2

segedunum Member since:
2005-07-06

He was talking about the attitude that is was okay to break APIs, is prevalent because of Linus.

He totally misunderstood that, which is probably why he doesn't understand a lot of things. To blame his mistakes and that of others on the kernel just shows how little he understands.

Linus has no qualms about breaking APIs within the kernel, but what the kernel did not do was break compatibility with userspace applications - i.e. external interfaces. That's something Linux desktop components have done time and time again.

Edited 2012-11-09 20:25 UTC

Reply Parent Score: 3

lucas_maximus Member since:
2009-08-18


He totally misunderstood that, which is probably why he doesn't understand a lot of things. To blame his mistakes and that of others on the kernel just shows how little he understands.


No he didn't misunderstand that, you guys keep on misunderstanding the fact it is about the attitude ... the specifics are not important.

Software Engineering is as much about attitude as it is competence.

Linus has no qualms about breaking APIs within the kernel, but what the kernel did not do was break compatibility with userspace applications - i.e. external interfaces. That's something Linux desktop components have done time and time again.


Oh goody ... well people <insert device> are still breaking after updates.

Reply Parent Score: 2