Slashdot Mirror


XFree86 Fork Gets a Name, Website

Piethein Strengholt writes "Today the Xfree86 fork is a fact. A new project has started and is located at: xouvert.org. Xouvert has been started due to the corporate structure and the slow development of XFree86. They hope to reduce the risk to XFree86 of incorporating new drivers and features."

3 of 647 comments (clear)

  1. For those who don't know... by nomis80 · · Score: 5, Informative

    "ouvert" means "open" in French.

  2. Re:Excellent by divec · · Score: 5, Informative
    However, X11's network transparency is just as creaky and obsolete as the rest of the beast. [...] the bandwidth and latency is just obscene when compared to Citrix Metaframe.

    See my previous comment on NX compression. I'm typing this on Galeon running at work, displaying on my home computer over a 56K modem, because it's faster web browsing like this than running the browser locally. NX has to be seen to be believed.

    The interesting thing is, this level of compression is only possible because of the high-level nature of X's network transparency - Citrix / RDP / VNC doesn't run anywhere near as fast.

    --

    perl -e 'fork||print for split//,"hahahaha"'

  3. Drop XFree86, use Y instead by Anonymous Coward · · Score: 5, Informative

    Frankly, it may be worth jettisoning a lot of the XFree86 baggage and starting anew.

    Y, an X Windows replacement, looks extremely well designed and this guy wrote a pretty complete implementation for his thesis.

    Why not port the useful bits of X - like the hardware drivers - over to this already-established well-designed base instead of trying to hack XFree86 into something of similar quality?

    (Well, the obvious answer, ``to keep the applications`` is fair enough. But a compatibility module wouldn't be too hard, and worth the benefit in the long run.)