Announcement

Collapse
No announcement yet.

Wayland's Weston Now Handles Full-Screen X Windows

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wayland's Weston Now Handles Full-Screen X Windows

    Phoronix: Wayland's Weston Now Handles Full-Screen X Windows

    In conjunction with XWayland, Wayland's Weston reference compositor can now handle full-screen X windows...

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

  • #2
    Waiting for Wayland's adoption has become a very sour experience. Just got a bitter taste in my mouth after reading this support won't be there officially until perhaps September. @_@ Crikey.

    Still, I'm sure its arrival will be as sweet as anything we could have aside from widespread support from major software developers.

    Comment


    • #3
      Originally posted by scionicspectre View Post
      Waiting for Wayland's adoption has become a very sour experience. Just got a bitter taste in my mouth after reading this support won't be there officially until perhaps September. @_@ Crikey.

      Still, I'm sure its arrival will be as sweet as anything we could have aside from widespread support from major software developers.
      It's mostly because they're slow to develop it, for a project that is an order of magnitude smaller and simpler than X like 5 years of development is a lot. In 2008 there was one dev then there were more and it still doesn't support the most basic stuff you need on a desktop, like subsurface stuff (for plug-ins etc).

      By trying to be (almost) perfect they're taking too much time which is a danger for them, at Canonical some assholes apparently are already planning to use their own stuff instead of Wayland.

      Comment


      • #4
        It is pathetic that Wayland takes so long to reach maturity since X is probably the only remaining HORRIBLE part of modern desktop Linux.

        Comment


        • #5
          Originally posted by varikonniemi View Post
          It is pathetic that Wayland takes so long to reach maturity since X is probably the only remaining HORRIBLE part of modern desktop Linux.
          I don't think they have a huge team in order to pull something like this fast. X i think has more people.


          And yes i am inpatient too and want it NOW. If i remember correctly there aren't much that need to be merged in order to have a usable desktop. (minus apps)

          Comment


          • #6
            I won't be using it on my desktop pc untill nvidia driver supports KMS anyway. Which I'm afraid will be never.

            Comment


            • #7
              Ah, the peanut gallery strikes again ^^
              Scream some more, maybe the wayland devs will actually get annoyed enough to care ( ..NOT).

              Comment


              • #8
                Originally posted by Ancurio View Post
                Ah, the peanut gallery strikes again ^^
                Scream some more, maybe the wayland devs will actually get annoyed enough to care ( ..NOT).
                Its not their problem/fault. We have established that wayland is designed in a way that it will be easy to get blobs work with it.

                Comment


                • #9
                  Originally posted by varikonniemi View Post
                  It is pathetic that Wayland takes so long to reach maturity since X is probably the only remaining HORRIBLE part of modern desktop Linux.
                  dont make me laugh. pulseaudio has latency issues so that you have to use a different mixer if you want low latency. i hope this is not an inherent flaw, cause if it is lennard should be hung from a lamppost.

                  Comment


                  • #10
                    Originally posted by varikonniemi View Post
                    It is pathetic that Wayland takes so long to reach maturity since X is probably the only remaining HORRIBLE part of modern desktop Linux.
                    Wayland should never be adopted as it is broken by design. It will just slow down applications compared to X without compositing.

                    Comment


                    • #11
                      Originally posted by 89c51 View Post
                      I don't think they have a huge team in order to pull something like this fast. X i think has more people.
                      Almost any project has more people. There is a huge shortage of developers in the Linux desktop space, despite hypothetical claims of FOSS allowing millions of eyeballs and hands. Microsoft has a test team for one small part of Windows that swamps the size of the developer pools for X/Wayland/GTK/GNOME combined. Turns out most people want to get paid for their hard work.

                      Comment


                      • #12
                        Originally posted by elanthis View Post
                        Almost any project has more people. There is a huge shortage of developers in the Linux desktop space, despite hypothetical claims of FOSS allowing millions of eyeballs and hands. Microsoft has a test team for one small part of Windows that swamps the size of the developer pools for X/Wayland/GTK/GNOME combined. Turns out most people want to get paid for their hard work.
                        Most wayland contributors are payed devs i think. Intel pays some, colabora some, the guy working on the input thing is payed and so on. Its just that there are few and no company as a whole is interested in desktop linux much. At least in advancing it.

                        Comment


                        • #13
                          Originally posted by JS987 View Post
                          Wayland should never be adopted as it is broken by design. It will just slow down applications compared to X without compositing.
                          Please explain. Broken by design is a much more serious accusation than merely a poor implementation.

                          Comment


                          • #14
                            Originally posted by blackout23 View Post
                            I won't be using it on my desktop pc untill nvidia driver supports KMS anyway. Which I'm afraid will be never.
                            /fail

                            The nvidia driver already supports kernel mode setting, they just have a proprietary implementation of it.

                            NVidia just has to support the buffer sharing API that Wayland uses, which should be simple.

                            Comment


                            • #15
                              Originally posted by garegin View Post
                              dont make me laugh. pulseaudio has latency issues so that you have to use a different mixer if you want low latency. i hope this is not an inherent flaw, cause if it is lennard should be hung from a lamppost.
                              Halfway: with pulseaudio, latency is tied directly to cpu usage, but there's an old and complicated api to ask for better latency. No guarantees that you'll get it, though.
                              Source: http://www.freedesktop.org/wiki/Soft...actencyControl
                              Of course, the OSS4 documentation points out that at least for video you only need ~30-40 millisecond latencies; the OSS4 developers state that they consider these normal latencies and claim that for single-digit latencies you need special hardware...Source:http://manuals.opensound.com/develop...io_timing.html

                              @JS987: I prefer X to wayland, but if you're bashing wayland, present some evidence.

                              Comment

                              Working...
                              X