
"X.Org Server 1.11 was
officially released this Friday evening. X.Org Server 1.11 was originally planned for released in mid August, but then the unfortunate passing of Keith Packard's mother (the X.Org release manager) led to a one-week delay. Our condolences go out to Keith Packard and his family. After numerous belated releases from X.Org in the past, a one week delay is nothing to complain about, especially considering the sad circumstance. While this is a new major X.Org Server release, it's mostly about bug-fixing. X Input 2.1 was delayed (with its touch-related features) to the next X.Org Server release (or later), there isn't any RandR extensions (after RandR 1.4 was restarted), and just nothing to get too excited over, besides addressing outstanding issues. Regardless, it's an improvement that incorporates six months of enhancements."
Member since:
2008-03-17
Network transparency is truly useful. Sure not to the majority of users out there, but then the majority of users feel that X.Org's performance is good enough.
Would people please shut up about network transparency. Yes, it is useful...
but network transparency as handled by X11 is really antiquated. None of the toolkits draw with X11 any more so the way things should be handled these days is that the toolkits should handle remote drawing.
Either way you can run x within wayland for all the applications that are not ported (much like Xquartz).
I'm under that category, besides, if you try out a Gnome 2 distro like Debian Squeeze, or Scientific Linux on some Core 2 processor (not even the current generation, or even less than that) you can feel how snappy it is compared to Windows 7. This is even without any compositing window manager.
I suggest you spin up that cpu with a heavy load and then check out the amazing snappiness. the thing here is that without compositing you're using the cpu for graphics, which is far more inefficient than using the gpu. Compositing isn't supposed to make things "snappier" just improve the experience (like not spinning up the cpu when drag gin windows etc).
Why would we drop all the driver compatibility just to get some more speed? I also understand Wayland is supposed to be cleaner, but X.Org has helped a lot by moving to a more modular way of doing things.
Either way, I see Wayland as a "well we want improvements, but we don't want to help the project that is out there 'cause we want to write our own!" mentality.
that isn't really an accurate characterization of the project. It is more like
"I wonder what I can do without being encumbered by X". Then everyone else jumping up and considering it a replacement instead of a research project (I imagine the excitement is due to people being fed up with all the craftiness found in X).
This mentality can be good, but really isn't when you're talking about something that is to most things as important as the kernel itself. Actually at this point in time, the kernel is even less important than X, since we have alternatives to the Linux kernel.
For one thing the Kernel is a lot younger than X. It also has far more developers and a structure that allows it to stay in continual development. X has very few developers and it's architecture frightens a lot of people away (there isn't much influx of new developers). If a more maintainable modern display server is used then chances are that new features are added more quickly and more developers join, two things that are the biggest weakness in X.