Linked by Thom Holwerda on Tue 20th Dec 2005 13:03 UTC, submitted by zam001
X11, Window Managers Aaron Siego of KDE: "It would be very nice if our X server could use OpenGL directly for its display and composition. Because then we could have hardware accelerated effects that are not only cool looking, but also very useful. Well, there is just such a project underway, called XGL. But don't hold your breath. The development of XGL has been largely removed from the community and is being done behind closed doors. Who is this company, you ask, that would take the development of something as potentially important as this out of the community and put it behind closed doors? Novell."
Thread beginning with comment 75961
To read all comments associated with this story, please click here.
OK.. so what?
by on Tue 20th Dec 2005 14:01 UTC

Member since:

They cant build it first and get it working then release it to the community? Just becuase it isnt being developed in the open initially does not mean when it is released it will not be released to teh community.
Maybe Novell realized that to get it out the door they couldnt sit there wrangling with all the political crap in the OSS community and decided that they would start it themselves.
I like the OSS method but sometimes it takes forever to get things off the ground because you have to bow to every person. They can forgo this if they build it and make an intial release and then release it to the community.

Reply Score: 5

RE: OK.. so what?
by on Tue 20th Dec 2005 14:07 in reply to "OK.. so what?"
Member since:

Actually they waited years for Xgl being developed (by only 2 active developers)

Xgl is way too large project for 2 developers, meaningless to say that it didn't even come close to usable/stabile X server ;)

Reply Parent Score: 1

RE: OK.. so what?
by bullethead on Tue 20th Dec 2005 14:10 in reply to "OK.. so what?"
bullethead Member since:

Exactly. Who cares about running alpha quality product. Let them bring it to market in at least a semi-workable state. The OSS community is good, but sometimes you don't have the time for distractions from the work and just want to get something done. Why does everyone insist that every single line of code should be on a cvs. When it's ready it's ready. When it comes out decide if it's good for you. All this protesting is ill.

Reply Parent Score: 5

RE: OK.. so what?
by on Tue 20th Dec 2005 14:13 in reply to "OK.. so what?"
Member since:

I believe you are right as long as the final product is open source. I agree with you until we see the code kept proprietary. It is not bad to close your ears and do some serious work, sometimes. s far as the lack of developers for X is concerned, the recent open solaris move maybe a positive action. The only problem I see with X is lack of documentation and serious tutorials (IBM can help here). When is the last time you saw an X-Windows book on amazon? I think the ammendment to X for the transition from R5 to R6 plus some very high level X books is the only source. We need more Xlib and X internals books from
O Reilly. Especially those books needed to write device drivers. R7 seems to provide more help.
Keep in mind that the transition from Xfree to Xorg is recent. We need time and tutorials, even for vga graphics. EXA and XAA + Xgl are not that documented. And please refrain from aswering go read the source code. I could not have learned C with reading programs only. Cheers.

Reply Parent Score: 2

RE: OK.. so what?
by on Tue 20th Dec 2005 16:09 in reply to "OK.. so what?"
Member since:

Open Source development is always about momentum.
If your initial idea is REALLY REALLY good then you can probably get developer interest with little or no effort or work on your part.

With a project like this, though , there isn't that much community interest in the project to begin with. if there was it would have been done by now, or there would have been 3 or 4 GPL projects which do the same thing.

Look ! There are different ways to start an Open Source Project. Sometimes you want to make architectural decisions before releasing it to the organic, sometimes unpredictable process of Open Source Development.

Give them a break and see what they do. If they botch it up they botch it up, but as it is ,there are no other projects out there trying to fill that need open or closed , We either should just shutup and code our own or let them continue in peace.

It's not that hard ladies and gentlemen. Quite the bickering

Reply Parent Score: 0

RE[2]: OK.. so what?
by on Tue 20th Dec 2005 16:49 in reply to "RE: OK.. so what?"
Member since:

"If your initial idea is REALLY REALLY good then you can probably get developer interest with little or no effort or work on your part. "
I find that to be somewhat to completely untrue. The only time Developers want to do something is if it is in their direct and best interest. Meaning they are scratching an itch or they are getting paid for the developement.
You could have the best idea on the planet, but if it does not coincide with what the developers are already doing it doesnt go anywhere.
Gnome developement is a good example of that. Where is the functional menu editor in gnome? The one they supply you with (2.12 branch) is so crippled to be worthless.
Xorg is another example, they had to fork to get where they wanted to go.
Consider this Novells fork.

Reply Parent Score: 0