Wayland 1.0 Officially Released

[Awesomeness]

honestly i don't care. the gui on linux is so messed up, it would be like painting a broken car.

Of course you care. If you didn't care, you wouldn't comment on a Linux-focused site.
You don't see me visiting any Windows-focused sites.

[garegin]

by i don't care I mean I am not holding my breath.

[89c51]

On the ML thread jbarnes talks about power savings (and memory) with wayland. Could anyone explain a bit more on this??

[drag]

On the ML thread jbarnes talks about power savings (and memory) with wayland. Could anyone explain a bit more on this??

Not sure.

My guess is that since Wayland is able to properly sync display updates with the refresh rate on the monitor and the applications can receive proper notifications when it comes to rendering a frame to display and such they can use the least amount of resources necessary to keep up with the display.

[drag]

Of course not, the protocol just became stable TODAY. GTK, EFL, QT, and KDE can all work on Wayland support because of the "scratch your own itch" nature of OSS. Nvidia and AMD arent going to spend money on developers to make their drivers Wayland compatible when they may have to turn around and redo all of it the next day.

QT and GTK already run in Wayland. I don't know about the rest.

IT's not terrible if they don't. Everything that currently runs in X will be able to run fine on Wayland because you will have a Wayland X server.

X Windows is a protocol. This is analogous to HTTP.
X Clients are your applications. This is analogous to Web Sites.
X Server is were your applications get rendered. This is analogous to a Web browser.

So running your X Server as the manager for your hardware is like running a Web browser that fiddles with settings on your PCI bus... which is a terrible design. In a well designed system there is no need to run a X Windows server that manages your hardware. It's a network protocol after all. Do you want something that listens on your network having direct access to your PCI bus and full root access to everything in your system?

So you will be able to run X windows applications on top of Wayland the same way you run Websites on Wayland... by using a application that implements X Windows.

Just like how you can run X applications on Microsoft Windows and on OS X... Microsoft Windows can even run GLX applications.

As far as Nviida proprietary drivers (which are the only proprietary drivers worth caring about) "supporting" Wayland.. all Wayland technically needs is EGL support.
http://en.wikipedia.org/wiki/EGL_(OpenGL)

People can already run Wayland on Android's graphic stack... I don't see why it would be a great leap to run it on Nvidia's graphic stack. Nvidia needs to support EGL on Linux anyways for embedded systems. It's natural that they would be able to support it on desktop systems.

Meanwhile Nvidia proprietary driver users will be able to run Wayland by running Wayland full screen on top of NVidia/Xorg X server until Nvidia decides to support the EGL extensions Wayland needs.

[asdx]

Of course not, the protocol just became stable TODAY. GTK, EFL, QT, and KDE can all work on Wayland support because of the "scratch your own itch" nature of OSS. Nvidia and AMD arent going to spend money on developers to make their drivers Wayland compatible when they may have to turn around and redo all of it the next day.

Qt, NOT QT.

[asdx]

QT and GTK already run in Wayland. I don't know about the rest.

IT's not terrible if they don't. Everything that currently runs in X will be able to run fine on Wayland because you will have a Wayland X server.

X Windows is a protocol. This is analogous to HTTP.
X Clients are your applications. This is analogous to Web Sites.
X Server is were your applications get rendered. This is analogous to a Web browser.

So running your X Server as the manager for your hardware is like running a Web browser that fiddles with settings on your PCI bus... which is a terrible design. In a well designed system there is no need to run a X Windows server that manages your hardware. It's a network protocol after all. Do you want something that listens on your network having direct access to your PCI bus and full root access to everything in your system?

So you will be able to run X windows applications on top of Wayland the same way you run Websites on Wayland... by using a application that implements X Windows.

Just like how you can run X applications on Microsoft Windows and on OS X... Microsoft Windows can even run GLX applications.

As far as Nviida proprietary drivers (which are the only proprietary drivers worth caring about) "supporting" Wayland.. all Wayland technically needs is EGL support.
http://en.wikipedia.org/wiki/EGL_(OpenGL)

People can already run Wayland on Android's graphic stack... I don't see why it would be a great leap to run it on Nvidia's graphic stack. Nvidia needs to support EGL on Linux anyways for embedded systems. It's natural that they would be able to support it on desktop systems.

Meanwhile Nvidia proprietary driver users will be able to run Wayland by running Wayland full screen on top of NVidia/Xorg X server until Nvidia decides to support the EGL extensions Wayland needs.

Qt, NOT QT.

Qt == Qt
QT == QuickTime

[Ancurio]

Qt, NOT QT.

Qt == Qt
QT == QuickTime

I think I can do that too!

GTK+, NOT GTK.

GTK is what it was called before turning object-oriented.

[disi]

Here is a Fedora wayland livecd:
http://people.fedoraproject.org/~rhughes/wayland/

Tested this morning in a KVM machine and cannot see much difference with Gnome3, if any at all. OK, KVM is extreme slow if it comes to 3D performance, so it was a little laggy but looks 100% the same as with Xorg-Server.

[blackout23]

Qt, NOT QT.

Qt == Qt
QT == QuickTime

OT:

QuickTime was when I started hateing Apple long before I knew about Macs and iPhones.
One player just to be able to play retarded *.mov videos. Almost as bad as Real Player back in the day.
QT sucks ballz. Thank god it is now meaningless like it should be.