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."
Thread beginning with comment 213922
To read all comments associated with this story, please click here.
by Headrush on Sat 17th Feb 2007 21:49 UTC
Member since:

Is it part of the the requirement of being a OSNews poster that we always have to read so much into comments?

I have no knowledge of the technical problems or workarounds in either code, (just like the majority of readers), but just because he didn't give a detailed presentation doesn't mean its not true.

Sure Beryl appears to be miles ahead of compiz in flash, but IF problems do exist, it is important that these are addressed and not hidden. Isn't this the kind of thing that has caused problems for MS over the years?

Whether most distros are choosing Beryl means nothing, as distro often grab what ever if the most flashy or currently usable.

I'm interested in if the plugin effects for either of these projects are going to be usable when the both KDE and Gnome have native/builtin compiz support. If things aren't planned properly, isn't this all spinning wheels no matter how cool it might look?

Edited 2007-02-17 21:58

Reply Score: 5