Linked by Thom Holwerda on Sat 17th Feb 2007 18:45 UTC, submitted by GhePeU
X11, Window Managers David Reveman writes: "I'd like to get all of you updated on the compiz related things discussed at the X developer conference that was held last week. My talk was mainly focused on 'what's next' and how to get desktop compositing in X to the next level." He also discussed the fork: "I had the chance to talk to Quinn Storm from the beryl project during xdevconf. I would have hoped that the current situation with beryl could be improved but it seems like Quinn at least isn't interested in that. However, after talking to Quinn it's very clear to me that the fork was partially motivated by assumptions that were wrong."
Permalink for comment 213934
To read all comments associated with this story, please click here.
RE: sour grapes?
by g2devi on Sat 17th Feb 2007 22:03 UTC in reply to "sour grapes?"
Member since:

It does sound that way. Some of the things he says makes sense (e.g. keeping the MIT license so as to allow code to be moved into, but it does seem that he is out of touch with Beryl and just plain FUDful (e.g. willing to accept code without too many questions and references to kludge after kludge). There's also mention that Beryl continues to use Compiz code and doesn't give back, but no mention that Beryl plugins have been ported into compiz-extra by Compiz developers (at least according to Wikipedia:

Here's a view from the other side of the fence:

You don't have to look too far to find it. It's directly on the main Beryl page in the "Planet" section.

Given the Beryl link and the Compiz link, my uninformed impression is that the real reason for the fork is something glossed on by both sides:

1) the Compiz team what's their code to get into and so they try to make it compatible with the low level code.

2) low level code is overly complicated out because of it's generality and the Beryl developers don't see the reason for the complexity if all you want to have is a window manager. That complexity makes it harder for new people to join Beryl so they want to spend a lot of time refactoring the code to make it easier for new people to contribute. The Beryl team also found other places that limited contribution and started working on reducing those.

The result? More people contribute to Beryl that would have with Compiz, and some plugins have been ported back to Compiz giving more plugins than would otherwise be the place, and finally some compiz work has (or will) get into which in turn allow Beryl to become better.

My own prediction is that Compiz will eventually disappear since the Compiz team's dream seems to be moving it's code into This in turn will give Metacity and KWin the ability to catch up to Beryl in most aspected except for support for multiple decorators and multiple configuration managers.

Reply Parent Score: 5