Linked by David Adams on Wed 10th Sep 2008 15:43 UTC, submitted by Michael Larabel
X11, Window Managers It has been one year and four days since X.Org 7.3 was released and a number of months since X.Org 7.4 was supposed to be released, but today X.Org 7.4 is scheduled to finally make it out the door! This release is shipping quite late and with a slimmed down set of features, but in this article we have more details on what this release holds in store for the Linux desktop community and why it may be a short-lived release.
Thread beginning with comment 330068
To view parent comment, click here.
To read all comments associated with this story, please click here.
abraxas
Member since:
2005-07-07

If you don't like it, help it. You didn't help, so you don't have the right to whine about it (well you do but it doesn't matter really what you say).

This is OSS, not a closed source company. If you PAYED for it then you have "some" right to whine, but not for a free OSS software you don't.

All projects out there need more people who GIVE BACK, something you obviously never heard about.


BS. How can you argue that I don't give back when you have NO idea? I do give back, but that's not even the point. Criticism isn't whining. Maybe you enjoy being misled but I don't. There is no reason for either OSS or proprietary software to promise so much and then under deliver several months late regulary. Something is broken. X releases have been problematic forever and someone has to get it straightened out. Projects like GNOME don't seem to have these kinds of problems. GNOME generally has a roadmap that they follow very closely. If something isn't finished in time they postpone the release, but it is never for very long because they haven't promised more than they can deliver. This is acceptable. Xorg releases are not.

It's not like I'm bitching about every little bug that I enounter, demanding that my problems be taken care of first. I just want to know "Where's the beef?". This release went way over schedule because of several new features being added that then weren't added at all and it still took a year! I don't see how anyone can be happy with that even X maintainers. It's a huge disappointment and anyone who says otherwise is in denial.

Reply Parent Score: 3

WereCatf Member since:
2006-02-15

This is where I step in to give my opinion, no matter if anyone is interested in hearing it or not.

X releases have been problematic forever and someone has to get it straightened out. Projects like GNOME don't seem to have these kinds of problems. GNOME generally has a roadmap that they follow very closely. If something isn't finished in time they postpone the release, but it is never for very long because they haven't promised more than they can deliver.

Indeed. Both GNOME and KDE are HUGE projects consisting of dozens of different packages but both projects are always on schedule and both seem to only promise what they know they can accomplish. But they have a different mindset from the beginning: promise what you know that can be kept, and don't start working on new features before the old ones are implemented. X developers seemingly rather start working on new features, discarding the promised ones, and delivering neither.

I am not saying they don't do good job. I couldn't do even nearly as good. But they need a roadmap and they need to stick to it. Jumping all over the place creates mess like this we've just got in our hands...

Reply Parent Score: 2

FooBarWidget Member since:
2005-11-11

If your goal is to encourage them to do a better job, then whining and complaining is possibly the worst way to achieve that. Everybody likes compliments, nobody likes people who whine and complain. And yet what do people do? They whine and complain when there are problems but say nothing when things are going well.

Think about this.

Don't even get me started on "constructive criticism". Most of the criticisms that I've seen on OSNews and Slashdot are far from "constructive". They're usually whines and complaints that the developer can't do anything with, even though seeing all that stuff it still affects them mentally in a negative way. It's surprising how many people think they're being "constructive" when in reality they're not.

If I'm an X.org developer it would be much easier for me to stop giving you free code and free support and to move on to something else. That would put you in an even worse position than before because now you've lost a person who does stuff for you for free.

Edited 2008-09-11 15:06 UTC

Reply Parent Score: 5

abraxas Member since:
2005-07-07

If your goal is to encourage them to do a better job, then whining and complaining is possibly the worst way to achieve that. Everybody likes compliments, nobody likes people who whine and complain. And yet what do people do? They whine and complain when there are problems but say nothing when things are going well.

Think about this.

Don't even get me started on "constructive criticism". Most of the criticisms that I've seen on OSNews and Slashdot are far from "constructive". They're usually whines and complaints that the developer can't do anything with, even though seeing all that stuff it still affects them mentally in a negative way. It's surprising how many people think they're being "constructive" when in reality they're not.

If I'm an X.org developer it would be much easier for me to stop giving you free code and free support and to move on to something else. That would put you in an even worse position than before because now you've lost a person who does stuff for you for free.



Well if you can't take criticism you probably shouldn't be in charge of a major project like X. We're not talking about grammar school children here, we're talking about adults. Coddling people's egos isn't going to get you anywhere. If you accept that status quo then obviously nothing is going to change and we'll continue to get ridiculously late and stripped releases. I never attacked X developers personally and I wouldn't because there is no need to. I simply criticised their release roadmap/scheduling. I think it's obvious that it deserves criticism.

Reply Parent Score: 2