Will Wayland Become A New Desktop Standard?

[MalleRIM]

Can someone please clarify for me?
So Wayland will be bundled with both compositor and window manager.. What about all the window managers we know and love? Pekwm? Fluxbox?

They are specifically X11 window managers and won't work. Actually, window management is done by wayland and window decoration by the clients, so there are no window managers needed anymore. From my understanding what has been the window manager can now become an implementation of a wayland server, server side decorations can still be used for those who want them - by telling the clients to not draw decorations and implement decorations in the server. Compiz for example wants to implement the wayland protocol.

[MaestroMaus]

The EGL and compositing sounds something that should be done in the Linux Kernel itself to be most efficient and integrated. Some kind of Linux EGL + OpenWF for compositing would greatly enhance compatibility and stability of applications.

Same for opengl (+es). The Linux Kernel should have a official reference software library (+version) for that API. Windows has that. Now mesa is an unofficial software implementation.

The LSB should ask for some improvements on the graphics side through use of EGL+OpenWF.

Oh please no. The Linux kernel is big and complicated already without all of the things you would like to see implemented.

[renkin]

Can someone please clarify for me?
So Wayland will be bundled with both compositor and window manager.. What about all the window managers we know and love? Pekwm? Fluxbox?

[md1032]

What puzzles me is why the people in graphics haven't already put X in bugfix only mode and dedicate resources in developing wayland.

Because the graphics developers are not amateurs and realize that reinventing the wheel is a *lot* harder than just adding bells and whistles to an already-working wheel.

[BenderRodriguez]

I wonder, can DBUS be used for Wayland instead of a custom socket protocol?

It probably could but i guess DBUS isn't fast enough for that kind of operations.

[Wyatt]

"Each Wayland Server implementation can provide its own distinct set of interfaces..." This is a joke, right? We're doomed.

Despite (or perhaps because) all of the raving, I remain sceptical. Oh, and adding another layer of indirection seems like a stupid idea. Really, what ever happened to Wayland being a set of experiments to test things that could be implemented in X.org or whatever the wording was?

I think far too many people are just going off the cuff about "ancient" code as if it's necessarily bad and new things are necessarily good.

PS: Remember that X.org is an implementation of the X11 protocol. "X" is ambiguous (or a robot).

[Lynden]

X definitely needs some work as far as compositing goes, but mend it, don't end it please!

Personally I don't mind if they replace X when Wayland has become stable enough for daily use.
X is 26 years old ('84), I'm sure the code base is a complete mess now of old code that's kept around purely for compatibility with ancient programs that virtually nobody uses any more on a recent desktop and code that's meant to add support for new graphic card features, window management, etc.

If Linux wants to go further on desktops then I don't think we can afford to keep this dinosaur around.
It served its purpose well for many years, but now it's just preventing us from going further.

[Cyberax]

I wonder, can DBUS be used for Wayland instead of a custom socket protocol?

[V!NCENT]

I've simply opened them all in tabs. Care for Phoronix bandwith I guess?

But it seems as if this will happen (if we put on the devil's Netcraft costume);
1. X will shrink to merely a protocol with nothing else left in it;
2. Wayland will run on top of what has been replacing X's (software) functionality;
3. X is a simple protocol will run on top of Wayland.

So basically they will be totaly and completely bundled.

[89c51]

The EGL and compositing sounds something that should be done in the Linux Kernel itself to be most efficient and integrated. Some kind of Linux EGL + OpenWF for compositing would greatly enhance compatibility and stability of applications.

Same for opengl (+es). The Linux Kernel should have a official reference software library (+version) for that API. Windows has that. Now mesa is an unofficial software implementation.

The LSB should ask for some improvements on the graphics side through use of EGL+OpenWF.

Benjamin Franzke is working afaik in implementing OpenWF over KMS (or something like that - he explained in a message here in the forum)


What puzzles me is why the people in graphics haven't already put X in bugfix only mode and dedicate resources in developing wayland.

Even if the only benefit of wayland was a "cleaner" codebase the benefits would be big. Plus it seems that more people (from companies=read potential money for devs) seem to be interested in wayland.