Slashdot Mirror


Wayland/Weston Gets Forked As Northfield/Norwood

An anonymous reader writes "Weeks after Canonical announced Mir, Wayland's display server protocol and Weston compositor have been forked. A contributor to Wayland found differing views with the project over desktop eye candy and other technical decisions to the X11 successor, which resulted in forming the Northfield and Norwood projects. The developer, Scott Moreau, has been outted from the project but has provided a lengthy explanation why the fork was needed to advance the Linux desktop."

5 of 252 comments (clear)

  1. "Advance the Linux desktop..." by Torodung · · Score: 5, Insightful

    "Advance." You keep saying that. I do not think it means what you think it means.

    What is needed, before "advancing" anything, is to advance acceptance of the Linux desktop, and IMHO this ain't helping.

  2. While the emerging display servers fight it out... by Bill_the_Engineer · · Score: 5, Insightful

    While the emerging display servers fight it out, I think I'll just stick to the tried and true X11.

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  3. Re:Survival of the Fittest by Anonymous Coward · · Score: 5, Insightful

    No. Instead of working together to resolve their differences and taking the best technical ideas from both groups to enhance the core product, they have a whiny bitch fest, split the development teams, create two products which end up lesser than the original, create an artificial need for more developers, reduce the advancement of the state of the art, and cause people new to the area to spend twice as long researching which products they should use.

    In the end, society loses.

  4. Re:Just what we need... by hawkinspeter · · Score: 5, Insightful

    If he's right, then maybe his fork will gain momentum. If he's wrong, then he'll be wasting some of his time, but I bet he'll learn from the experience either way.

    Often it takes someone to branch out and start something to jumpstart development so that other people see what's been done and think it's worth contributing to. Unless someone makes that jump, we'd never know what might have been.

    --
    You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
  5. Re:More information by serviscope_minor · · Score: 5, Insightful

    The core protocol is flawed

    Bullshit!

    The core protocol is very very good.

    There are a fewnow obsoloete bits like the bitmap graphics and fonts, but the rest of the core is fundementally sound.

    So, unless you can provide some evidence that the protocol is flawed, then go back under your rock.

    Oh yeah and Keith Packard: quotes don't count. He might be a core X11 developer but he's also a one man FUD machine, which is really sad.

    About a bazillion extensions.

    So? Let me repeat that, so?

    The protocol is *designed* for extensions. Extensions are simply the X equivalent of adding more API calls.

    Look at Linux: it is a POSIX kernel, but with LOADS of extensions! Does anyone whine "oe woe posix is flawed linux has so many extensions it's fundementally broken lets nuke it stard from scratch and by the way no one needs multi user right?"?

    Seriously, who the fuck cares if they're "extensions" or "core", any more that if I care if the networking zero copy super low latency fast stuff is an extension or in the core POSIX system call interface? A clue: no one cares.

    No one cares on Windows either! Turns out that Windows 8 implements all those Win32 calls right back to the Win32S (a Windows 3.X era thing) API. Do you hear anyone complaining that because Windows has some old API calls in it that it is fundementally flawed and the mere existence of old APIs taints it? No, because that would be stupid.

    Likewise: you know OSX used to allow you to run OS9 and earlier binaries! My got it supports old stuff!! It must be fundementally flawed! Oh my god! Every system supports some degree of backwards compatibility!! They are ALL FLAWED! We must rewrite them all in javascript on the cloud in HTML5 except that all the browsers can render HTML 3.1 so they are flawed too!!!

    Here's what astonishes me: people hate X so much that they complain (a) when it's too old and (b) when the developers add API calls to make it more up to date!

    Actually, I'm in favour of updating the core protocol, or adding some hefty extensions to reduce latency NX style---though XCB actually is a fair improvement over xlib---but Wayhand is not the answer to that because it removes basically everything.

    --
    SJW n. One who posts facts.