Linked by the_randymon on Wed 9th Jan 2013 00:48 UTC
X11, Window Managers Lead developer for Compiz, Sam Spilsbury, says he sees little need to develop Compiz for Wayland due to the increasing fragmentation of the Linux ecosystem. Spilsbury writes "What does compiz actually provide to users of these systems? [...] None of this functionality that user wants really depends on our compositing engine. There's nothing so special about our compositing engine that gives it a reason to exist [...] This is the real practical toll of fragmentation amongst the Linux ecosystem. It's not just that there are multiple implementations of the wheel. There are multiple implementations of entire cars which do almost the same thing, but a little different from everyone else. Some say this is the free software's greatest strength. Now that I know the personal and technical toll of fragmentation, I see it as its greatest weakness."
Thread beginning with comment 547954
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: What an utter non-sense
by dsmogor on Wed 9th Jan 2013 14:27 UTC in reply to "RE[2]: What an utter non-sense"
Member since:

Wayland is fundamentally a protocol with a ref impl., and he wanted to avoid replicating current mess with X11 window managers with equivalent mess of competing wayland implementations, that in the end some poor souls have to maintain and debug inside of Linux companies that loose money on that.

Reply Parent Score: 2

Gullible Jones Member since:

I don't see why the current situation with window managers is "a mess," actually (other than that X11 itself is a mess). One size does not fit all.

Reply Parent Score: 3

RE[5]: What an utter non-sense
by dsmogor on Thu 10th Jan 2013 09:39 in reply to "RE[4]: What an utter non-sense"
dsmogor Member since:

It's about 2 things:
- wasted effort (as author notes WM is much much more complex to get right than it appears)
- bugs, inconsistencies, and variances in implementations that cause headaches to application developers.
What the author suggests is not forcing simple functionality set upon everybody throat but simply promote the common (hard) part to a common system library / service that could then be extended implementing different policies people need.
Wayland, being the new, virgin ground is the best opportunity for that.

Reply Parent Score: 3