X.Org Server 1.15 Should Be Released Next Week

[phoronix]

Phoronix: X.Org Server 1.15 Should Be Released Next Week

The last planned X.Org Server 1.15 release candidate is now available ahead of the planned official release next week...

http://www.phoronix.com/vr.php?view=MTU0ODA

[uid313]

DRI3, Present extension, GLX rewrite, fuck yeah!

Too bad XWayland isn't part of it yet.

[MartinN]

Too bad XWayland isn't part of it yet.

My sentiments exactly. Wish Keith or anyone from the X camp would say something about why the delay?

[adrr]

My sentiments exactly. Wish Keith or anyone from the X camp would say something about why the delay?

Why should they help the competition? That feature is suicide.

[Ericg]

Why should they help the competition? That feature is suicide.

Hey look guys! New troll's first post. Its not 'the competition,' the X devs KNOW how bad the Xorg server code is, but they cant break all the stuff they need to break because they have to follow "The X Standard." Hence DRI3 and Present, it gets X as close to Wayland as possible without BEING wayland. Watch the XDC2013 talks and the linux.conf.au talks, its tons of the devs ripping on how bad X's architecture is and how asinine some things are

[adrr]

Hey look guys! New troll's first post. Its not 'the competition,' the X devs KNOW how bad the Xorg server code is, but they cant break all the stuff they need to break because they have to follow "The X Standard." Hence DRI3 and Present, it gets X as close to Wayland as possible without BEING wayland. Watch the XDC2013 talks and the linux.conf.au talks, its tons of the devs ripping on how bad X's architecture is and how asinine some things are

So they are not competing and the X developers themselves try to kill xserver?

[KellyClowers]

Hey look guys! New troll's first post. Its not 'the competition,' the X devs KNOW how bad the Xorg server code is, but they cant break all the stuff they need to break because they have to follow "The X Standard." Hence DRI3 and Present, it gets X as close to Wayland as possible without BEING wayland. Watch the XDC2013 talks and the linux.conf.au talks, its tons of the devs ripping on how bad X's architecture is and how asinine some things are

That, and the Xorg team and the Wayland team have a very high degree of overlap, and the Xorg guys were the ones that started Wayland...

[alanc]

My sentiments exactly. Wish Keith or anyone from the X camp would say something about why the delay?

From the X.Org side, there is no delay - the people writing the code are still working on it and have never sent a pull request stating that Xwayland is ready to be merged into the master branch. Code takes time to write and debug, and when the underlying code base continues to evolve during that time, then it takes more time to resync. It was never going to happen overnight.

[MartinN]

From the X.Org side, there is no delay - the people writing the code are still working on it and have never sent a pull request stating that Xwayland is ready to be merged into the master branch. Code takes time to write and debug, and when the underlying code base continues to evolve during that time, then it takes more time to resync. It was never going to happen overnight.

Thank you.