Announcement

Collapse
No announcement yet.

Wayland 1.20 Planned For Release In December

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

  • Wayland 1.20 Planned For Release In December

    Phoronix: Wayland 1.20 Planned For Release In December

    It's been nine months since the release of Wayland 1.19 while now release plans have been drafted for Wayland 1.20...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    So FreeBSD supports Wayland now?

    Comment


    • #3
      Why does it feel like it's already dead Jim? Or everyone is content with the status quo? X.org, though it was a fork of XFree86, saw a ton of development in its early years.

      Comment


      • #4
        And I was hoping for some kind of screen capturing API.

        Comment


        • #5
          Can it recover from GPU hangs?
          Can it update GPU device driver without restart?
          Can it support secure attention key login using Ctrl+Alt+Del?

          Comment


          • #6
            Originally posted by uid313 View Post
            Can it recover from GPU hangs?
            Can it update GPU device driver without restart?
            Can it support secure attention key login using Ctrl+Alt+Del?
            "That's outside the protocol, please consult with your DE compositor" - Wayland developers.

            Comment


            • #7
              Originally posted by birdie View Post
              Why does it feel like it's already dead Jim? Or everyone is content with the status quo? X.org, though it was a fork of XFree86, saw a ton of development in its early years.
              In what universe does Wayland seem dead? What else do you think is necessary for a display server and protocol to have? Because I'm guessing a lot of those features are things that either:
              A. Are what made X11 into a bloated, broken, and insecure mess
              B. Go beyond the definition of a protocol and display server, and therefore should not be implemented
              Also, Wayland was released in 2008; it's hardly in it's "early years" anymore.

              Comment


              • #8
                Originally posted by Danny3 View Post
                And I was hoping for some kind of screen capturing API.
                That already exists at the compositor level

                Comment


                • #9
                  So let me get this straight.. On one hand, Wayland compositors have to reinvent the wheel because of the protocol's minimalism. On the other hand, that's what Wayland developers want, because they don't want to turn into a "bloated mess" like x11. Can't there be some middle ground in this situation?
                  Last edited by user1; 29 October 2021, 08:25 AM.

                  Comment


                  • #10
                    schmidtbag

                    Out of two dozen people on Phoronix who continue to scream that X.org is insecure, not a single has been able to demonstrate any in-the-wild malware using the said "insecurity" of even past real incidents/breaches/successful hacking attempts related to it.

                    As for "bloated", are you a programmer or you're parroting what you've once heard? How much experience in C programming do you have to say something like that? Do you have experience in writing display drivers or other other low-level enough code? Wayland might have been released in 2008, it doesn't make any more well-thought-out or suitable for the desktop.

                    Comment

                    Working...
                    X