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 213964
To read all comments associated with this story, please click here.
RE[3]: sour grapes?
by apoclypse on Sat 17th Feb 2007 23:49 UTC in reply to "RE[2]: sour grapes?"
apoclypse
Member since:
2007-02-17

Exactly. Beryl doesn't deal with the internal of x the way compiz does, because frankly the beryl devs don't know how, that much is obvious by beryl itself. The fact is if things are done correctly from the get go, they wouldn't have reimplement things correctly later. Chances are when things do get implemented correctly its not going to be code coming from the beryl devs instead they are going to be using code from compiz, getting all the benefits and giving very little back to the project that started the whole thing to begin with. What the beryl devs have done is pander to every fool out there who wants eyecandy, implement a hack to get it working, giving the user a perceived "better than compiz" impression because compiz won't pander to every idiot request being put out there. The fact is beryl got forked because of the hacks that were being put into it. Dave has always maintained that everything should be implemented through plugins and if can't be done with plugins THEN update the core. Beryl took a different approach and instead was patching the core left and right for something that shouldn't be done there in the first place. The biggest example is the BSM, the beryl devs claimed that compiz relied to much on Gnome, when in-fact this wasn't true at all, compiz was made to have any backend implemented through plugins. The beryl devs took it upon themselves to implemented an extremely hackish settings manager that btw still relies on gtk. Guess what when they wanted to be considered to be the default Wm in ubuntu (composite by default spec) they had written themselves into a corner and had to rewrite it.

Edited 2007-02-17 23:54

Reply Parent Score: 5