Slashdot Mirror


Wayland 1.2.0 Released With Weston

An anonymous reader writes "Wayland 1.2 & Weston 1.2 have been released. Features of this quarterly update to the X.Org/Mir display competitor is support for color management, a new input method framework, a Raspberry Pi renderer/back-end, HiDPI output scaling, multi-seat improvements, and various other changes for this next-generation Linux desktop display protocol and compositor."

122 comments

  1. Looks good! by CajunArson · · Score: 4, Interesting

    Wayland & Weston are coming along pretty well and we are seeing increased adoption in both GTK+/QT toolkits and in desktops with upcoming versions of KDE.

    One area where the developers need to go out and evangelize is on the front of EGL for proprietary drivers. Yes it's great that Intel's open source drivers (and to a lesser extend the open-source AMD & Nvidia drivers) have EGL support, but both AMD & Nvidia need to be convinced that EGL is important to their upcoming proprietary drivers too.

    The irony here is that Mir, which is is seen as a huge competitor to Wayland, could end up helping Wayland enourmously since Canonical doesn't seem to be afraid to pick up a phone and call people at AMD/Nvidia to talk about updating the drivers.

    --
    AntiFA: An abbreviation for Anti First Amendment.
    1. Re:Looks good! by Anonymous Coward · · Score: 0

      One things is for sure, ServiTroll_Major is going to be pissed about this. I forecast heavy trolling from him any moment now.

    2. Re:Looks good! by Anonymous Coward · · Score: 0

      Yes, that grass sure is growing!

    3. Re:Looks good! by diego.viola · · Score: 0

      Qt.

      Not "QT"

      Qt is the correct name.

      QT is often confused with QuickTime.

      Please write it correctly the next time to avoid confusion. Thanks.

    4. Re:Looks good! by unixisc · · Score: 1

      Anybody knows whether and when the BSDs - PC-BSD and others - will have Wayland available? Also, will KDE 5 and beyond continue to run on X as well, or just Wayland?

    5. Re:Looks good! by AdamWill · · Score: 1

      "The irony here is that Mir, which is is seen as a huge competitor to Wayland, could end up helping Wayland enourmously since Canonical doesn't seem to be afraid to pick up a phone and call people at AMD/Nvidia to talk about updating the drivers."

      Well, no, Canonical is not afraid to print loud press releases about how they're talking to AMD/NVIDIA, couched as confusingly as possible to make it sound like AMD/NVIDIA are already confirmed riders on the Mir train. It's a publicity exercise. I'm sure the Wayland developers are in touch with AMD/NVIDIA as well, they just aren't as cynical as Canonical about trumpeting it loudly in press releases.

    6. Re:Looks good! by KugelKurt · · Score: 1

      The irony here is that Mir, which is is seen as a huge competitor to Wayland, could end up helping Wayland enourmously since Canonical doesn't seem to be afraid to pick up a phone and call people at AMD/Nvidia to talk about updating the drivers.

      Take a minute or five and browse nvidia.com.
      What you'll discover is that for GPGPU business NVidia officially only supports the latest OS releases by three companies: MS Windows Server, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server.
      What you won't find is official support for Ubuntu 12.04 LTS.

      And while it's a pretty safe bet that RHEL 7 won't support Wayland (it's said to be based on Fedora 19), it's certain RHEL 8 will support it and NVidia will support RHEL 8. The chances are high that NVidia will "beta test" the drivers on Fedora before the RHEL 8 release.

  2. third post! by fredan · · Score: 4, Funny

    since I'm using X11 ;-(

    1. Re:third post! by Anonymous Coward · · Score: 0

      If you are using X11 - should that no be 12th post ?

    2. Re:third post! by Anonymous Coward · · Score: 0

      At least you have a clean client/server model instead of riding the short bus to MS Clippy / iOS / autocorrect (/ ShowView / automatic gearbox) land.

    3. Re:third post! by crazyaxemaniac · · Score: 1

      The client/server model is not a Wayland problem.

      From presentations I've seen from the developers the talking points I've heard are:
      * X11's client/server protocol has lots of round-trips that make remote applications respond slowly.
      * X11 has a client/server model but newer toolkits end up transferring bitmaps over the wire and in this case the RDP/vnc is better or at least no worse.
      * If an X11-like client/server protocol is desired the toolkits are in a better position to implement something X11-like that sends drawing instructions over the wire.

    4. Re:third post! by Anonymous Coward · · Score: 0

      Client / Server is fundamental to thin clients.

    5. Re:third post! by Anonymous Coward · · Score: 0

      My thin clients use ICA and RDP. Oh you weren't talking about Wyse and Citrix? (You know what 99% of the thin client world actually uses..)

    6. Re:third post! by crazyaxemaniac · · Score: 2

      Client / Server is fundamental to thin clients.

      There's a vnc/rdp client is about as thin as you get. Wayland compositors can do this. What else is needed?

    7. Re:third post! by jbolden · · Score: 1

      Absolutely it is. Being able to control round trips is fundamental to thin clients working on a WAN as opposed to a LAN environment.

    8. Re:third post! by Guy+Harris · · Score: 1

      At least you have a clean client/server model instead of riding the short bus to MS Clippy / iOS / autocorrect (/ ShowView / automatic gearbox) land.

      And you couldn't implement Clippy and auto-correct in an X11 desktop or desktop atop another "clean" client/server window system? (And if "iOS" refers to any of the various sins ascribed to iOS, what about them couldn't be implemented in an X11 interface?)

    9. Re:third post! by jbolden · · Score: 1

      iOS uses some very low level hardware based systems that don't work with X11. X11 for example doesn't allow for an h.264 movie as a graphical primitive with its own hardware based rendering system that can't go back and forth between buffers. Similarly for the camera.

      More importantly the ram requirements would be a substantial problem. 1.2m per screen with 3 screens for layers with 60 ftps. Double that up again for the extra X11 buffers and you are out of ram already before you have any code. Which means you either have to finish your screen computations twice as fast or not use X11's buffering strategy.

    10. Re:third post! by Guy+Harris · · Score: 1

      iOS uses some very low level hardware based systems that don't work with X11. X11 for example doesn't allow for an h.264 movie as a graphical primitive with its own hardware based rendering system that can't go back and forth between buffers. Similarly for the camera.

      More importantly the ram requirements would be a substantial problem. 1.2m per screen with 3 screens for layers with 60 ftps. Double that up again for the extra X11 buffers and you are out of ram already before you have any code. Which means you either have to finish your screen computations twice as fast or not use X11's buffering strategy.

      I wasn't saying "why couldn't X11 be used for iOS?", I was saying "which of the various sins ascribed to iOS couldn't be done atop X11?", with "the various sins ascribed to iOS" referring to the "ZOMG IT DOESN'T DO MULTITASKING"/"ZOMG IT HAS DRM"/"ZOMG ONLY APPLE-APPROVED APPS CAN RUN ON IT"/"ZOMG IT DOESN'T LET APPS DO XXX" stuff that shows up here. The poster to whom I replied spoke of "MS Clippy / iOS / autocorrect (/ ShowView / automatic gearbox) land", in which context "iOS" sounds as if it's referring to that sort of higher-level stuff, not to low-level window system details (which is why that poster was being so spectacularly silly).

    11. Re:third post! by Anonymous Coward · · Score: 0

      Agreed with all points but the last. Toolkits are NOT in a better position to implement an X11-like protocol, because there are many of them. The only beautiful thing about X11 is that it is a standard.

    12. Re:third post! by Anonymous Coward · · Score: 0

      No, you didn't get my point at all.

      The things I mentioned are all examples of nightmare scenarios of utter dumbing-down, where it has become so "simple", that it is catastrophically inefficient, limiting and useless, and serves no other purpose than to cater to people who are so lazy that they harm themselves by crippling their own abilities for "simplicity"'s sake. People who ride the short bus. (Ok, that's an insult to the actual mentally disabled people. They don't have a choice. But these people here do.)

      iOS and Win8 are worst case scenarios (until they invent something even worse). They are really downright crippling.

      And Canonical, Ubuntu, Gnome3 , Wayland... it's all coming from that same bunch of mock-educated retards with the same fucked up "KISS"/Apple mindset.

    13. Re:third post! by Guy+Harris · · Score: 1

      And Canonical, Ubuntu, Gnome3 , Wayland... it's all coming from that same bunch of mock-educated retards with the same fucked up "KISS"/Apple mindset.

      Please offer evidence (rather than a rant) that Wayland is "coming from that same bunch of mock-educated retards with the same fucked up "KISS"/Apple mindset".

    14. Re:third post! by Anonymous Coward · · Score: 0

      Yeah, and Obama should provide his long-form birth certificate too. Because that will *totally* stop their disbelief...
      Please provide evidence that your opinion isn't already set in stone.

      Because if you had ever looked at Wayland, the e-mails of its developers, used iOS, Gnome 3, Ubuntu, Windows 8, etc, and did so with open eyes, you would have detected a pattern long ago.

  3. Jolla will use Wayland too by Anonymous Coward · · Score: 0

    Jolla's upcoming Linux-based mobile will also ship with Wayland. Makes sense, as it became clear recently they'll also use Qt 5.0. Good to see them jumping on new tech early on.

    1. Re:Jolla will use Wayland too by Anonymous Coward · · Score: 0

      Jolla's upcoming Linux-based mobile will also ship with Wayland. Makes sense, as it became clear recently they'll also use Qt 5.0. Good to see them jumping on new tech early on.

      this time last year they said they would ship a device by xmas last year.

  4. Wrong Summary by allo · · Score: 2, Informative

    Wayland ist not a Xorg/Mir competitor, as mir is not affiliated in any way with xorg. Wayland is the planned successor of Xorg, while Mir is some Ubuntu project.

    1. Re:Wrong Summary by brodock · · Score: 2

      Mir is another alternative/competitor to Xorg... the difference is that Mir is following the idea of a rigid protocol where Mir is following the idea of providing an API... both of then have drawbacks... but I'm confident that Mir could win the run. History has prooved that its not the "perfect engineered solution" that always win... Despite of what you think... in the end... its all about user adoption.

    2. Re: Wrong Summary by Anonymous Coward · · Score: 1

      I read that thing about "rigid protocol vs api" from shuttleworth's blog, and I still can't figure out how it isn't complete bullshit.

    3. Re:Wrong Summary by Anonymous Coward · · Score: 0

      You are mentioning Mir twice. Which one is what Mir provides? The rigid protocol or the API?

    4. Re:Wrong Summary by Anonymous Coward · · Score: 1, Interesting

      Except it's complete bullshit. Read the announcement: Wayland 1.2.0 now provides a stable server API (it already provided a stable client API since 1.0.0) as well as a rigid protocol. Everything, everything, that has been said about Mir being better then Wayland is Grade-A Pure Bullshit. Also, Mir will lose because nobody else is ever going to use it. Wayland: all Linux distros except Ubuntu (including all commerically supported distros like SLE and RHEL). Mir: only Ubuntu. Hell, even the Ubuntu derivatives like Kubuntu and Xubuntu have publically stated they won't use Mir!

    5. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Indeed, more than that, by self-admitted design, Mir is pretty much a back-end for Unity only. Other desktops will have to use XMir, i.e. X11 running full-screen on top of Mir. Presumably on day there will be a Wayland–Mir compatibility layer

      Mir is an ally for getting KMS/EGL support from the drivers though.

    6. Re: Wrong Summary by Anonymous Coward · · Score: 0

      Mir provides the API.

    7. Re:Wrong Summary by westlake · · Score: 1

      Wayland is the planned successor of Xorg, while Mir is some Ubuntu project.

      Given the client-side success of Ubuntu and OEM support for Ubuntu, Mir can't and shouldn't be casually dismissed.

    8. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Still not a "competitor" since Mir is essentially a Canonical-only technology that no other distribution plans to adopt. In the fairly near future, Wayland will pretty much be the standard Linux display technology, used and supported by a wide variety of distributions and developers. Mir and all the other dependent components will be Ubuntu-only and users will be tied to the ability of Canonical, and only Canonical, to support all that software with timely updates and bug fixes.

    9. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Why is parent getting modded up? Of course Mir is a competitor. This is just flamebait/trolling

    10. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Mir is for Unity, and Ubuntu wants to do things which Wayland will not. Ubuntu isn't trying to make a display server for everyone, in fact they aren't even making one for anyone else but Unity. This gives them some advantage, because they can do what they want.

    11. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Still not a "competitor" since Mir is essentially a Canonical-only technology that no other distribution plans to adopt.

      Which is irrelevant since no one uses the other distributions.

    12. Re:Wrong Summary by allo · · Score: 1

      because you're not understanding the posting.

      Mir IS a competitor, as i said in my posting. But it is not Xorg/Mir vs Wayland, but Xorg/Wayland vs. Mir. Wayland will be a successor of Xorg, while Mir is a totally different Project. Of course, Wayland is no X11+1, but a different project, too. But the developers now seem to agree, that Wayland is a good software to replace X11, while Mir is Ubuntu's NIH-Project.

    13. Re:Wrong Summary by allo · · Score: 1

      okay, now you justed outed yourself, that you're just a troll.

    14. Re:Wrong Summary by Anonymous Coward · · Score: 0

      Mir will never amount to anything unless it makes it into projects outside of Ubuntu. Unfortunately Canonical has never shown the ability to swim upstream.

      Pulse Audio would never have made it if it stayed in Red Hat distributions. PA developers sent patches to hundreds of other projects adding support. People tend to think that it was somehow exclusively tied to "distribution adoption" but that adoption would not have been possible at all if PA didn't send patches to desktop environments, applications, and assorted toolkits that were OUTSIDE of the PA project. It was also wasn't immune to outside influence itself.

      Canonical still doesn't understand effective open source development. Don't develop in private. Don't expect adoption without sending admissible patches outside of your project. You have to do something more than say "ta-da! everyone's on board." Misleading PR won't make this happen.

  5. any decent tiling WMs? by Trepidity · · Score: 2

    Is Weston the only choice, or is there anything vaguely analogous to i3 or dwm in terms of how windows are laid out and managed?

    1. Re:any decent tiling WMs? by Anonymous Coward · · Score: 0

      You could always run i3 or dwm via X on Wayland.

    2. Re: any decent tiling WMs? by Anonymous Coward · · Score: 0

      Weston is a sample Wayland server/window manager. It's not expected to be used for most people.

    3. Re:any decent tiling WMs? by raxx7 · · Score: 4, Informative

      Yes and no.

      Weston is only a reference implementation of a Wayland compositor.
      Wayland developers don't expect it actually to be used by normal users.

      Instead, they expect others to implement their own Wayland compositors, as it should not be any harder than writing a similar X Window Manager.
      That is what the Gnome, KDE and Enlightmenment people plan to do, convert their current X compositors (gnome shell, kwin, e) into Wayland compositors.

      So, eventually, you might get a dwm Wayland equivalent. But it doesn't exist yet.

    4. Re:any decent tiling WMs? by Anonymous Coward · · Score: 0

      Aside from that pretty much defeating the point of running Wayland at all...

    5. Re:any decent tiling WMs? by jbolden · · Score: 1

      From what I've heard, window managers are much harder to write for Wayland than for X11 but there is an expectation there will be several in a few years. It isn't going to be like X11 though where you can create a basic window manager as a classroom assignment.

    6. Re:any decent tiling WMs? by hobarrera · · Score: 1

      Weston is a replacement for Xorg; it's the reference implementation for Wayland, NOT a window manager.

    7. Re:any decent tiling WMs? by AdamWill · · Score: 1

      GTK+ and Qt already have Wayland compositors, AIUI.

  6. The Real Story Behind Wayland and X.org by Anonymous Coward · · Score: 2, Informative

    Daniel Stone made a great presentation explaining various problems with X11 that Wayland tries to fix:
    http://mirror.linux.org.au/linux.conf.au/2013/ogv/The_real_story_behind_Wayland_and_X.ogv

    The same presentation is also on YouTube:
    https://www.youtube.com/watch?v=RIctzAQOe44

    1. Re:The Real Story Behind Wayland and X.org by jbolden · · Score: 1

      Good video link by the AC. Worth checking out.

    2. Re:The Real Story Behind Wayland and X.org by cheesybagel · · Score: 3, Informative

      What I did manage to grasp from his talk is that the basic X design which he claims is terrible has remained for the most part while their fantastic new designs for things like XInput keep getting obsoleted one after the other. That he does not like the fact that X11 has a lot of extensions so his answer is to rewrite it. What will eventually happen if he ever has success is Wayland will get a lot of cruft as well.

      I also noticed he gave no demos of Wayland at all. He isn't even eating his own dogfood. At least the original X designers actually created it to solve a problem they had and they actually used it.

      His model of doing everything using pixmaps is also probably going to be a problem if displays keep going to higher resolutions as is happening recently. In that case you may spend a lot less bandwidth sending draw calls rather than the pixmaps.

      I also disagree about the claim that VNC is good enough.

    3. Re:The Real Story Behind Wayland and X.org by complete+loony · · Score: 2

      What I'd like to see built as a replacement for X11's network abstractions, is a sandboxed VM running on top of the display server, passing arbitrary messages back and forth with the remote application.

      For example, take the llvm based pNaCl sandbox that the google Chrome team are building. Expose wayland API's for updating and displaying window pixmaps, and receiving input.

      Then you could port the widget libraries from a UI toolkit to run directly in this VM without imposing any limits to creativity and future innovation. Visual feedback for a drag operation or button push can then be animated immediately on the display, while a simple event message is sent back to the host application to trigger further processing.

      Plus the application developer could implement arbitrary custom widgets and have the same low latency interaction with the user.

      I'm not suggesting that the entire application should be run in this sandbox, but in some cases that may be acceptable too.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    4. Re:The Real Story Behind Wayland and X.org by Kjella · · Score: 3, Insightful

      What I did manage to grasp from his talk is that the basic X design which he claims is terrible has remained for the most part

      What has remained are the parts that you really can't replace without ceasing to be X11, he goes to great lengths to explain how toolkits, compositors and extensions all try to work around it. It's the reason they want to replace X11 with Weston, not the other way around.

      while their fantastic new designs for things like XInput keep getting obsoleted one after the other.

      Or as others would call it, getting new features. Do I smell a case of WORKS4ME? Didn't need it, don't want it so nobody else should either, X11 is just fine the way it is.

      I also noticed he gave no demos of Wayland at all. He isn't even eating his own dogfood.

      It was a presentation not a demo, don't pretend you can't find demos on YouTube... There are even LiveCDs so you can try it yourself.

      His model of doing everything using pixmaps is also probably going to be a problem if displays keep going to higher resolutions as is happening recently. In that case you may spend a lot less bandwidth sending draw calls rather than the pixmaps.

      Which would be relevant if anybody was using X as a drawing library, but nobody does that anymore. There is OpenGL pass-through with GLX, but the final image acts like a pixmap to the X server and I assume there will be something similar with Wayland, in fact as I understand it that's the only way Wayland will work as it has no drawing routines of its own.

      --
      Live today, because you never know what tomorrow brings
    5. Re:The Real Story Behind Wayland and X.org by dbIII · · Score: 1

      What I'd like to see built as a replacement for X11's network abstractions

      Sockets - been there since before the first official release.

      passing arbitrary messages back and forth with the remote application.

      Is ssh what you are looking for? X thinks it's all local and ssh feeds the remote stuff to and from the local display, using those sockets that have been in there for years.

    6. Re:The Real Story Behind Wayland and X.org by Dog-Cow · · Score: 1

      Try reading the whole comment before posting.

    7. Re:The Real Story Behind Wayland and X.org by jbolden · · Score: 1

      The basic design for X... not really. The basic design for X does a great job of solving the problem of solving the problem of how to distribute workload on a LAN when servers can do the complex graphics while clients can't. That's not the situation anywhere. Motif is not the way things are done. Everyone is constantly trying to get around the basic design for X because they want to shift workload from the servers (X-Client) to the client (X-Server). So no I don't think the basic design has lasted.

      As for Wayland getting cruft. The idea of Wayland is that hopefully it fits the model and gets tossed when the model no longer fits.

      As for "eating his own dogfood" he was specific, he is going to start using Wayland himself when he fixes Mutter as a compositor so that GNOME can run on Wayland plus one other to-do.

      As for VNC good enough, he said it was better than X. Wayland has always pushed for an RDP type solution.

    8. Re:The Real Story Behind Wayland and X.org by dbIII · · Score: 1

      Of course I did.

    9. Re:The Real Story Behind Wayland and X.org by Anonymous Coward · · Score: 0

      What I'd like to see is you and grandpa getting hit by a cluetruck. Network transparency has to be done RDP style, in real life X11 is nothing more than terribly slow VNC without compression, you can't get worse than that, especially since Wayland is expected to have VNC-like networking. And shut about your networked X11 pahformance, there's no way streaming hundreds and thousands of megabits per seccond could be fast, in fact, streaming 1080p over GigE will max out the theoretical bandwidth of it and that's not counting in X11 overhead or audio And good luck networking OpenGL. But your xterm works just as slowly as locally? Sure, but my Konsole run locally and using SSH for remote shell access complete with transparent compression is way faster, and it's a lot easier to attach and detach existing shells (try that with X11, I dare you, fools!).

      Also, grandpa, you are epically confused, modern day X11 is nothing but pixmaps and sending drawing commands (e.g. RDP) can only be done by the toolkit which is what Wayland authors originally intendeded to force upon the world. Everything you said about Wayland is actually the current state of things regarding X11 and Wayland is the soltuion.

    10. Re:The Real Story Behind Wayland and X.org by complete+loony · · Score: 1

      Sure, use RDP instead of X11. It gives a reasonable display, with minimal latency between the client and server, and reasonably minimal complexity. Now try bouncing your network connection off the moon. Did I really hit that button? It doesn't look like it has changed.

      What you really want is a local process to animate the button push. But locking you into using a motif style X11 button limits future innovation. And what about other kinds of user feedback?

      Web browsers have thrived for many types of applications, as they give you a standard(-ish) rendering engine, a standard way to talk to remote applications, with a small amount of scripting support. But you can't always fit a round peg into a square hole.

      So why not allow a application to run some code in a sandbox, with resource limits, and remove all other restrictions.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
  7. Benchmarks please by dbIII · · Score: 0, Troll

    Will those "X sux and wayland is the answer" put up some numbers (they don't even have to good ones just something to show future promise) or shut up?

    1. Re:Benchmarks please by Anonymous Coward · · Score: 0

      I read in the Wayland documentation that the primary motivation for Wayland is that it's a fresh start. The objective is to be able to drop support for old X11 functionality. I think that's a worthy enough cause.

      And while they're at it, they are implementing Wayland with a new vision where (as far as I understand) the server is just a resource manager that gets the client in direct touch with the hardware. The work is done in the libraries.

      I'm not sure I'd like the applications running directly on local hardware. Rather, imagine a Qt Server local to the Wayland server. The Qt toolkit would convert Qt method calls into messages and messages back into signals (callbacks) while the Qt Server takes care of the Widgets, themes and such. That would probably enhance, rather than sacrifice, the network transparency of X11. You could then run a GTK Server next to the Qt Server so you wouldn't be stuck with one technology.

    2. Re:Benchmarks please by Anonymous Coward · · Score: 0

      Since you asked so nicely, I tested Weston recently. While performance was about the same when comparing Weston and X, the Weston implementation used significantly less RAM. In the range of 50-75% of what X was using for similar operations.

    3. Re:Benchmarks please by TheRealMindChild · · Score: 1, Interesting

      For starters, me and many others wanted an accelerated desktop for the Raspberry Pi. Through the shitty documentation and poor ass code structure, I couldn't come close to figure out how to write a video driver for X. In Wayland, you have a reference implementation (Weston) to build one. That alone is a huge advantage

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    4. Re:Benchmarks please by Anonymous Coward · · Score: 0

      Not numbers, but it does at least seem to perform better on lower-end hardware:

      http://www.hardware.slashdot.org/story/13/05/27/227242/vastly-improved-raspberry-pi-performance-with-wayland

    5. Re:Benchmarks please by dbIII · · Score: 1

      is that it's a fresh start

      Which is misleading because it uses the X hardware drivers.

    6. Re:Benchmarks please by Barsteward · · Score: 1

      Go and watch Daniel Stone's 2013 presentation for info from the horses mouth

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    7. Re:Benchmarks please by kriebz · · Score: 1, Interesting

      Actually, your observation is misleading. Graphics drivers on Linux have been using a lot of Linux features for a long time to improve performance, implement modern features, and handle hardware management in the kernel, where it belongs. No rule says that code can then only be used by X. They are Linux drivers, not X drivers.

    8. Re:Benchmarks please by multi+io · · Score: 1, Informative

      Will those "X sux and wayland is the answer" put up some numbers (they don't even have to good ones just something to show future promise) or shut up?

      Sometimes when you're fiddling with context menus too much, you manage to lock up the X server completely -- all you can do is move the mouse pointer, which at this point mostly points north-east or has turned into a cross.

      Whenever an X client is somehow busy, does something bad or hogs up resources, the whole server freezes, sometimes periodically for half a second every two seconds or so. You can see it e.g. during graphically intensive redraws, or when Chrome loads several tabs simultaneously -- all the animations in the tab headers stop periodically, and the mouse pointer freezes at the same times. When I opened a few Chrome tabs too many lately, the load skyrocketed up to about 60, and the machine was inoperable for 10 minutes, before calmed down again, on its own. This has happened more than once too. These may in part be implementation issues (Xorg being single-threaded and all), and I don't know how well Wayland does in those kinds of situations, all I know is that the OSX display server fares much better. Individual clients may freeze, but the compositor always works, the mouse pointer never freezes, and you never see half-drawn frames or other random artifacts.

    9. Re:Benchmarks please by jbolden · · Score: 3, Interesting

      Sure.

      Speed of light 186,282 miles per second
      Speed that a human can detect jitter of an icon tracing a finger 1/100th of a second
      size of the earth 26k miles
      circumference of the earth 24,901
      fastest possible a round trip can occur from the worst 2 spots on the earth assuming 0 latency beyond the speed of light: .0683 seconds
      or the earth is about 7x too big for X11 to work.

      Chance of us being able to fix either the speed of light or the size of the earth 0%

    10. Re:Benchmarks please by jbolden · · Score: 1

      sorry .0683 seconds is for a one way trip. Round trip is double that. i.e. earth is 13.5x too big.

    11. Re:Benchmarks please by dbIII · · Score: 1

      They are the driver written for xorg and not for the linux kernel.
      Which reminds me - a major drawback of Wayland is it is designed around some features that only exist in linux and not in other versions of *nix. Whether that will be corrected later (as happened when gnome started the same way) or not remains to be seen.

    12. Re:Benchmarks please by dbIII · · Score: 1

      Nice joke, but could I get an answer from a grown up please?

    13. Re:Benchmarks please by dbIII · · Score: 1

      That's X - please answer the question and tell me how your chrome usage on Wayland behaves under the same conditions.

    14. Re:Benchmarks please by Anonymous Coward · · Score: 0

      No, they are the Linux kernel driver, written for the DRI2 API.

    15. Re:Benchmarks please by Anonymous Coward · · Score: 0

      A grown up would go and do a bit of their own research, and try it out for themselves, rather than whine impotently on an anonymous internet site, about how nobody is doing them a favor.

    16. Re:Benchmarks please by serviscope_minor · · Score: 1

      Seriously, how the hell is the parent post a troll.

      These articles are always full of X sux trolls. How is asking for some evidence trolling?

      --
      SJW n. One who posts facts.
    17. Re:Benchmarks please by dbIII · · Score: 1

      No, the people making the extraordinary claims are the ones that are expected to provide evidence of it. They have not which is why I am asking for it.

    18. Re:Benchmarks please by jbolden · · Score: 1

      X11 is permanently unfixable. That's not a minor issue. A grown up is going to tell you that latencies over the public internet is worse than that and with QoS becoming more important and mobile latencies are likely to increase over the next generation.

    19. Re:Benchmarks please by jbolden · · Score: 1

      The poster is pretty well known to dismiss good answers he's gotten over the years.

      The problems with X11 start at things like the number of round trips the client and server have to engage in. Anyone can watch the protocol chat back and forth in RAM and them imagine that they were on a connection with 100ms, 200ms latency....

      It isn't hard to do the math for some of these bad cases:
      150 round trips x 200 ms latency = 3 seconds till the window gets finished drawing.

      Anyone who has used X11 over a WAN has seen this problem for themselves.

    20. Re:Benchmarks please by dbIII · · Score: 1

      Even worse is there are so many replies yet nothing better than someone hoping for a fast display on a Pi and the usual Wayland ignorant fanboy pretending to be stupid with some speed of light calcs to make fun of me.
      I wish these guys would learn about the software they are pushing instead of just parroting something they've heard second hand.

    21. Re:Benchmarks please by dbIII · · Score: 1

      Another post supplied some hope that you were going to treat this seriously but now you're off again into the land of wild irrelevant claims insulting the intelligence of the readers. Could you please push off and let somebody who actually knows something about Wayland or X reply?

    22. Re:Benchmarks please by jbolden · · Score: 1

      Wayland already has a FreeBSD port in progress for the last 5 months.

    23. Re:Benchmarks please by jbolden · · Score: 1

      So far

      you've claimed there is no non-Linux solution when there has been one since Feb
      you didn't know about benchmarks
      you didn't know about them finishing the port of FreeRDP

      I'd say you might want to change you tone about who doesn't know stuff about X or Wayland.

    24. Re:Benchmarks please by dbIII · · Score: 1

      you didn't know about benchmarks

      I still don't know - hence the SUBJECT HEADING, and instead of pointing me somewhere where I can find out you go on with joking rubbish (totally irrelevant to a local display) about the speed of light and the size of the earth implying that networking in general is useless.

      If I knew about Wayland I wouldn't be asking about it. What pisses me off is if anyone who has a clue about Wayland is replying they are hiding their clue very well.

      So then, how about proving you are more than just a fanboy that has heard of the thing but never even seen it and pointing out where those benchmarks I'm supposed to know about are?
      Also where's the non-linux solution and how does it get around Wayland being tied specifically to the current linux device model? Also, if it has actually existed for less than six months how do you expect somebody outside the group of wayland developers and fans to have heard about it - that's a bit steep to hold against me. If it is true (and your other posts don't fill me with confidence on that), wouldn't it be far better to present it as a correction instead of an accusation?

    25. Re:Benchmarks please by serviscope_minor · · Score: 2

      The problems with X11 start at things like the number of round trips the client and server have to engage in.

      If we're talking about WAN network connections, then yes. For local stuff, people still complain about X being slow, but the data just doesn't support it.

      150 round trips x 200 ms latency = 3 seconds till the window gets finished drawing.

      X is a bit chatty. There seem to be several reasons.
      1. The protocol itself is a bit too chatty. This could be improved greatly if the server could push out events for certain things so that the client can cache them reliably.

      The NX people have essentially shown that this is indeed possible and the NX extended protocol seems to be one of the best remote graphical displays to use over a WAN.

      2. People can't code X11 protocol for toffee. A classic example is making heavy use of XInternAtom as a synchronus call. In fact Keith Packard himself uses that as a reason for X11 having problems. If you need 100 atoms, you have to wait for 100 round trips.

      Interestingly though in the protocol this is not a synchronus call. The newer XCB binding actually has it as an asynchronus call and in fact one of the first examples in the XCB documentation is how to get all your atoms in a single round trip.

      Xlib (not X11) is substantially at fault. The correct thing (implementing a new C binding, namely XCB) has been done. However, even with Xlib, toolkit authors seem to love working under the assumption that they're working locally and misuse the protocol in all sorts of bad ways, making round trips where none are necessary.

      --
      SJW n. One who posts facts.
    26. Re:Benchmarks please by jbolden · · Score: 1

      I agree with you X11 in theory could be designed to work better with WANs. I also agree that NX has somewhat demonstrated that. Your comment about toolkit authors focusing on locally is interesting. But I don't think that unusual. I think ultimately though that

      a) Local
      b) LAN
      c) WAN

      require often opposite optimizations. If Wayland takes over the local case X11, freed from having to worry about local at all might be able to become a far better WAN protocol. I just think it is unlikely that what works well for (a) should work well for (c) and visa versa. If I have 100ms I want to buffer to make sure I don't have to fetch again. If I have .1ns latency I want to fetch again and avoid the expense of the copy involved in buffering.

      (b) which is X11's sweet spot is a very rare use case in 2013.

  8. Can I run Wayland on top of X11? by caseih · · Score: 1

    Is it possible to run a Wayland display server in a big full-screen window on X11? That would be a fairly easy way to test wayland out and develop using the wayland GTK or Qt libraries. One huge advantage to this would be that I don't need to wait for driver support. As long as X11 had a driver, I'd be good to go. Since Wayland would be writing through (presumably) openGL to a full screen window, none of X11's asynchronous speed problems would be noticeable; waylands renderings within the window would all be snappy and synchronized. Granted too many layers of redirection could become a problem.

    This is a similar idea (stop-gap of course) to what SuSE did years ago with the old Xglx project, which ran on top of X11 and opengl, which was eventually phased out in favor of AIGLX and Xrender.

    1. Re:Can I run Wayland on top of X11? by jbolden · · Score: 2

      X11 runs on top of Wayland. I imagine you might be able to run Wayland on X11 by creating a fake screen but it could be brutally slow. Pretty much, yes you have to wait for driver support.

    2. Re:Can I run Wayland on top of X11? by Anonymous Coward · · Score: 1

      Weston will launch fullscreen on X11 which may given you what you want. ./weston --fullscreen

      There's a build script for Wayland here which builds it under Debian:
      http://www.chaosreigns.com/wayland/buildscript/

      I believe arch linux has an AUP for Wayland and Debian sid has binaries for the most recent versions.

    3. Re:Can I run Wayland on top of X11? by Tailhook · · Score: 2

      Yes. Specify the x11-backend.so when starting Weston and it runs on top of X.

      --
      Maw! Fire up the karma burner!
    4. Re:Can I run Wayland on top of X11? by serviscope_minor · · Score: 2

      X11 runs on top of Wayland.

      X11 can run top of Wayland. It doesn't necessarily.

      I imagine you might be able to run Wayland on X11 by creating a fake screen but it could be brutally slow

      If you do it badly, sure.

      Wayland wants the world to be a collection of draw buffers (i.e. one per window more or less). There's no reason you couldn't simply have one X11 window for each Wayland window. Given it's all GL all the way down and X11 supports pretty much the fastest 3D graphics so far, I don't see why it would be slow.

      --
      SJW n. One who posts facts.
    5. Re:Can I run Wayland on top of X11? by jbolden · · Score: 1

      I guess that's true. If you wrote a protocol so that each Wayland client believed it was talking to a Wayland compositor while really that was code running on the X-Server, and the X-Server took information from the X-compositor and transformed it into Wayland-compositor messages it would be possible to do that. That's a lot of work though.

      I don't think anyone is doing it. So the answer is that's man years that no one intends to spend.

    6. Re:Can I run Wayland on top of X11? by spitzak · · Score: 1

      Yes you can run Wayland inside an X window. It does this automatically if $DISPLAY is set when wayland is run. This is in fact the only way I have gotten it to work. It is certainly a requirement for Wayland development right now. I have two monitors and I just run it fullscreen in one of the monitors, with the launching terminal in the other one so I can see error messages.

      For me it uses the X shm interface to transfer the pixmaps from Wayland to X (I believe it may just transfer a single image that corresponds to the entire desktop). For me this works surprisingly well though. It may be slow, but the lack of async update between the various portions makes things like moving and resizing windows actually look smoother.

      Apparently it can use EGL for this instead. The Wayland pixmaps are transferred as EGL images and composited into the desktop image using the EGL driver in the X server. This would be vastly faster. However this does not work under the Nvidia X drivers.

      I'm not sure if it is related, but Wayland clients can use either EGL or shm (unrelated to X shm, but using Linux shm with fallback to files in /tmp) to send images to Wayland. The EGL api has never worked for me, probably due to some interference from the Nvidia X driver though I can't figure it out. This must not be an uncommon problem, as most of the demo Wayland clients now detect that EGL will not work and use shm in that case (the one called simple_egl fails however). I don't think this was intended, I think they hoped EGL would be used always. It looks to me that if EGL worked from the clients and in talking to X, the wayland-on-x stuff would pass the EGL buffers right through and composite them in the X EGL driver, and this should be pretty close to full speed.

  9. Remoteability question restated by LaughingRadish · · Score: 5, Interesting

    Here's a very simple question with hopefully no wiggle room: Suppose I have two Linux boxes, each running Wayland. They do not run X11 in any form or fashion. I am on the console of one of them and in Wayland. Can I start a terminal emulator, ssh over to the other box, issue a command that starts some graphical program (which uses only Wayland coding, no X11), and expect that program's window to show up on the first box? Assume that ssh has already been modified to allow for this sort of thing. If this cannot be done, what prevents it from being done? I have yet received no complete answer for this.

    1. Re:Remoteability question restated by Anonymous Coward · · Score: 0

      Currently? Nope. In a few years? yes.

      The problem is that unlike X there is no ubiquitus Wayland process sitting on the system managing remote calls, so the modification to SSH or whatever the devs decide to do might be a bite more involved.

    2. Re:Remoteability question restated by jbolden · · Score: 2, Informative

      Wayland is going to be implementing some like RDP to handle this. Wayland natively does not handle this. So if your question is in terms of "Wayland as it is likely to exist" then likely you will be able to do it. If your question is "Wayland by itself with none of the supporting ecosystem" no. On the other hand normal screen sharing stuff like VNC would work.

      What prevents it from being done is that Wayland applications share their graphical and application buffer. You can't pull it apart without virtualizing the entire screen like VNC.

    3. Re:Remoteability question restated by LaughingRadish · · Score: 1

      Thanks. This is the most direct answer I've gotten so far. A followup: How much work has been done on that part of the supporting ecosystem to support remoting?

    4. Re:Remoteability question restated by jbolden · · Score: 1

      Lots of experiments and some of the initial testing, more or less a functioning prototype. My opinion is the functional version will be in the next version of KDE/GNOME: KDE 5 and GNOME 4 and that's if all goes reasonably well.

    5. Re:Remoteability question restated by Anonymous Coward · · Score: 0

      So in about 5 years or so? KDE and GNOME don't do major versions very often, and I don't think either has another major version on the horizon at the moment.

    6. Re:Remoteability question restated by jbolden · · Score: 1

      That would be my guess to you have a genuinely useful remote system rather than cool proof of concepts.

    7. Re:Remoteability question restated by dbIII · · Score: 1

      It's something the wayland developers do not consider to be a feature worth implementing at this time so the only answer you'll get are guesses as to how it may be done later. I wish the wayland people would discuss their thing on it's own merits instead of pretending it can do everything that X does better when it really has different aims.

    8. Re:Remoteability question restated by dbIII · · Score: 1

      The last link I found on that was from a couple of years ago where the "more or less a functioning prototype" didn't work at all when he tried out his idea and the developer moved on to other things. Care to provide something that refutes that or is it something completely out of your field?

    9. Re:Remoteability question restated by Anonymous Coward · · Score: 0

      No! The Wayland developer suggests using VNC or a similar Remote Desktop tool for this task.

      What you are asking for is called Network Transparency. In Wayland and Mir it is being sacrificed for the sake of looking prettier.

      In my opinion, using a Remote Desktop protocol to forward a single application GUI just seems wrong. I don't want to install a full blown Desktop on a machine on which I'll bring up the jmx console every other week for troubleshooting

    10. Re:Remoteability question restated by jbolden · · Score: 1

      sure the port of FreeRDP by Kristian Høgsberg into Wayland is much more recent.

      http://lists.freedesktop.org/archives/wayland-devel/2013-March/007740.html

    11. Re:Remoteability question restated by dbIII · · Score: 1

      Finally some sort of answer! Very ugly and inefficient hack but it's early days so likely to improve. Next how about something along the line of benchmarks like I've been asking for since about six wayland articles ago? Obviously not remote ones since it's far too early, just something about performance feeding pixels to the local video hardware would be nice. Since the argument is about the loss of flexibility being worth the performance gain I don't think that is too much to ask.

    12. Re:Remoteability question restated by hobarrera · · Score: 1

      AFAIK, RDP lets you see the entire remote screen, not the windows of a single program. There's a big difference. Imagine GIMP; with xorg+ssh you get 4 floating windows. With RDP, you have a the remote desktop with 4 windows inside of it. You can't stack remote and local windows as freely.

    13. Re:Remoteability question restated by jbolden · · Score: 1

      That depends on the application. The applications has to be able to accept RDP as a shell and then the "alternative shell" commend from Windows allows it to open in RDP as a single applications.

      \Unix programs using RDP, even today, have never had that problem because they expect to run in different shells. So until GNOME apps absolutely positively won't run in anything but Gnome, or KDE apps absolutely won't run in anything but KDE we should be fine.

    14. Re:Remoteability question restated by KugelKurt · · Score: 1

      AFAIK, RDP lets you see the entire remote screen, not the windows of a single program.

      https://github.com/FreeRDP/FreeRDP/wiki/RemoteApp

    15. Re:Remoteability question restated by KugelKurt · · Score: 1

      What you are asking for is called Network Transparency. In Wayland and Mir it is being sacrificed for the sake of looking prettier.

      If by "looking prettier" you mean anything more fancy than monochrome rectangles, then yes. However anything more fancy than monochrome rectangles isn't network transparent on X11 either. See https://www.youtube.com/watch?v=RIctzAQOe44 for details.

  10. Benchmarks by dbIII · · Score: 1

    Where are the benchmarks to back up all the claims that it is better than X? Even something showing catchup or even a degree of usability would be nice.

  11. Many advantages to Mir by OrangeTide · · Score: 1

    The other advantage is that Canonnical can cock it up without affecting anyone else.

    --
    “Common sense is not so common.” — Voltaire
  12. I'd better spell it out by dbIII · · Score: 1

    To avoid time wasting trite rubbish light speed of light stuff, what I mean above is the performance in terms of how long it takes for the application to call for something to be drawn, then it going through the layers to the compositor before being sent to the video hardware. I still remain unconvinced by block diagrams that hide internal complexity which is why I keep asking for benchmarks.

  13. Can someone with a clue reply instead? by dbIII · · Score: 1

    What was the point of posting a Mir benchmark to a question about Wayland?
    Were you hoping I would not follow the link and you could tell yourself you had won some sort of childish mass debate game? Until now you had me half considering you may know what you are writing about. Can someone with a clue reply instead in?

    1. Re:Can someone with a clue reply instead? by jbolden · · Score: 1

      Because it is the same approach and Mir is further along. Wayland isn't at the benchmarking phase yet they are still getting stuff to work at all.

      What is your damage? Why it works in theory is clear. Microsoft, Apple and early systems show how well it works in practice. Mir proves it works well in practice for Unix. You want good quality benchmarks of well know Unix apps running on both X11 and Wayland wait till 2016 or so.

    2. Re:Can someone with a clue reply instead? by AdamWill · · Score: 1

      "Because it is the same approach and Mir is further along. Wayland isn't at the benchmarking phase yet they are still getting stuff to work at all."

      Um. No. Phoronix benchmarked XMir. XWayland, which is precisely the same thing for Wayland, has existed in usable form for months or years.

    3. Re:Can someone with a clue reply instead? by dbIII · · Score: 1

      Because it is the same approach and Mir is further along

      No it most definitely is not. Why are you lying?