Linked by Thom Holwerda on Tue 10th Feb 2009 17:13 UTC
X11, Window Managers Ever since its inception, there have been problems with Compiz; people unsatisfied with the direction of the project forked it, then they merged again. Recently, the project, now known as Compiz Fusion, faced other problems, such as multiple branches and a lack of direction. A major reorganisation of the project is supposed to fix all this.
Permalink for comment 348269
To read all comments associated with this story, please click here.
RE[2]: Comment by Calipso
by siride on Wed 11th Feb 2009 15:16 UTC in reply to "RE: Comment by Calipso"
siride
Member since:
2006-01-02

I'll add to this by saying that compiz went the wrong way by being a standalone WM. What should have happened is that all the compositing and effects work that went into compiz should have been put into a library that other WMs could have used and then have KWin, Metacity, XFWM, heck, even Fluxbox, be able to make use of those features, but otherwise integrating with the existing DEs/WMs that people actually want to use. As it stands now, Compiz has its own configuration system, its own theming system, its own horrible window management system, etc. Yes, there are plugins to try to connect to native backends, but that's really the wrong solution. Compiz should itself be the backend, with existing WMs, configuration systems and theme systems working as they did before.

Reply Parent Score: 2