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."
"ouvert" means "open" in French.
Xouvert is the project that xwin.org was put in place to instegate.
Drop the network transparency, make it run framebuffer and XFree is obsolete on desktop.
Why do people not realize, that X-Windows is NOT sucking because of network transparancy! Any possible design of a clean API for a windowing system will more or less be automatically network transparent. The only this which is not network transparent are stupid ugly hacks. That said, we all know how X sucks, but it is has definitively nothing to do with network transparancy.
Cheers
KdenLive/PIAVE - non-linear video editing
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"'
Only the proxy is GPLed, the Xlib stuff is X11. The proxy is a separate program, so thats ok.
What is really needed is a driver for the XServer that will duplicate the current X command stream. This could then be sent to the NX proxy, and actually use it as a remote desktop. Also could use VNC, and it could also be useful for providing desktop pagers with full update capability.
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.)
Yes, it's starting as an experimental branch from XFree. Other experimentals include:
- GCC/EGCS
- Emacs/XEmacs
- Minix/Linux
- BSD4.4/OpenBSD/NetBSD/FreeBSD
See a pattern yet? They are doing their own source tree, their own code control, etc. This is not a branch of the official XFree86 project. This is a fork, which will be maintained independently of XFree86. It seems that one of two things will happen here.While I'm not against going out on a limb and doing something innovative, I just wonder if it would have been better to try and accomplish this within the project that currently exists?
Overrated / Underrated : Moderation
If you've ever managed a reasonably large open source project then you know that making everything public from the beginning won't necessarily be a good thing!
You can't just dump some stuff somewhere on the net and then expect people to contribute. You have to prepare a lot of things, so that people can easily contribute without getting lost in the mess!
And I don't know who moderated you up but those moderators certainly didn't read the website. I quote:
"Sat Aug 16 00:59:49 PDT 2003 - You can't download anything yet. We have this website, XWIN is providing Wiki space, and Savannah is providing mailing list and bug tracking services. We are importing the Xfree86 source code into an arch repository right now; the current job is making a script to tag the source files every time a CVS checkout is done. The IRC logging bot still needs to be set up, and code written to archive the logs daily."
The website has only been up since yesterday! Accusing them for "keeping it secret" and shoot down their image is just stupid, when they've just started recently.
It was referencing comments on Mosfet (a ex-KDE developer who was kicked off the KDE development team)'s personal webpage. Mosfet himself said that it wasn't true after talking with more people (e.g, Havoc) later on his webpage (mosfet.org/mosfet.arklinux.org, which is down currently-- moving)
Yes it's compatible. X11 is a protocol, not an implementation. XFree86 is an implementation. Xouvert will be another implementation of the same protocol.
Maybe you are looking for this-
http://xf4vnc.sourceforge.net/
:. Ultimate Control Dedicated/VM Servers
Linux is pronounced LIE-nucks.
On kernel.org you can find the correct pronunciation.
Do you care about the security of your wireless mouse?