Because very often, the people with the best insights are the ones who aren't in a position to do anything about them. If we're only going to take criticism from the people who know how to do fix or organise things, then GNOME is never going to pass its tipping point.
#2: It is not about criticism. Talk is cheap. Too many people discuss things on end without doing anything. And you do not have to be a coder to actually do something. It usually stays with blue sky ideas / long thread.. then... nothing.
#3: all software has bugs (except maybe TeX). Further, the existence of bugs doesn't mean decadence. The meaning of decadence is 'period of deterioration or decline'. GNOME has improved a lot since 2.0. If your point was about sucky software, that is an opinion.
6 comments:
Does “his” (in the phrase “his bugs”) refer to Benjamin or to the author (referring to himself as “/me”)?
Because very often, the people with the best insights are the ones who aren't in a position to do anything about them. If we're only going to take criticism from the people who know how to do fix or organise things, then GNOME is never going to pass its tipping point.
Fixing bugs < not making sucky software in the first place. Decadence, say I.
Parce qu'on ne dit pas "la somme d'individualités GNOME" mais : "la communauté GNOME". That's why...
Code speak better than words.
So let people talk, and spend our timing coding and making things rock.
To the two anonymous comments:
#2: It is not about criticism. Talk is cheap. Too many people discuss things on end without doing anything. And you do not have to be a coder to actually do something. It usually stays with blue sky ideas / long thread.. then... nothing.
#3: all software has bugs (except maybe TeX). Further, the existence of bugs doesn't mean decadence. The meaning of decadence is 'period of deterioration or decline'. GNOME has improved a lot since 2.0. If your point was about sucky software, that is an opinion.
Post a Comment