Announcement

Collapse
No announcement yet.

PCSX2 Emulator Disables Wayland Support By Default

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

  • #71
    Originally posted by Sonadow View Post
    . Blame Gnome, Plasma and Sway for not getting it right even after a decade into Wayland.
    100% agree gnome wayland, plasma wayland, sway wayland and pcsx2 wayland all suck. I haven't found anything wayland that doesnt suck.

    But its a none issue. Dont blame them. Just use the X11 and be happy. Ive been wayland free for a few years now, and dont have any problems.
    Last edited by mSparks; 27 November 2023, 09:41 AM.

    Comment


    • #72
      Originally posted by Sonadow View Post

      The fact Gnome has these internal APIs is proof it's entirely possible for a compositor to do what needs to be done for all these sore points about screen sharing and control under Wayland. There's nothing to stop Plasma and wlroots from following suit.

      If desktop Linux would finally wake up and converge on these three compositors as the Wayland compositors for Linux, many of these problems will have been solved by now.

      I rather deal with three internal APIs *now* and start selling my products *now* than wait another 7 years for these three internal APIs to finally become one common API.
      yeah, if we would drop the compositor jungle and would only have one, it would be easier. Like with xorg, where there was only one.

      Why do we switch to Wayland again?

      Comment


      • #73
        Originally posted by Sonadow View Post
        That's the problem with the compositor and not Wayland the protocol. Blame Gnome, Plasma and Sway for not getting it right even after a decade into Wayland.
        no, it's because no wayland protocol is suitable for this use case, Wayland is explicitly designed to need everyone to agree on protocols. when they don't agree, it doesn't happen, it's a critical benefit and flaw of wayland. that is explicitly an issue with the wayland protocol.

        Whatever your complaints are, Gnome is still the most performant and usable Wayland desktop environment to date compared to the other two.
        KDE is far more preformant then gnome is. Gnome stutters when opening a bloody notepad on lower end hardware.

        Comment


        • #74
          Originally posted by Sonadow View Post

          The fact Gnome has these internal APIs is proof it's entirely possible for a compositor to do what needs to be done for all these sore points about screen sharing and control under Wayland. There's nothing to stop Plasma and wlroots from following suit.

          If desktop Linux would finally wake up and converge on these three compositors as the Wayland compositors for Linux, many of these problems will have been solved by now.

          I rather deal with three internal APIs *now* and start selling my products *now* than wait another 7 years for these three internal APIs to finally become one common API.
          It's also proof that RHEL is using Wayland to EEE people into GNOME. Instead of creating a shared system everyone can benefit from, they extend or propose to extend the Wayland protocol and only implement it in GNOME and Mutter so only they benefit.

          They get to show the world how great, altruistic, and open they are while that exact same action directly stifles and hampers their competition. It's brilliantly nefarious. And if anyone says anything people start repeating the "But, but, but it's only a protocol" mantra like that means something while the rest of are like, "No shit. It's just a protocol is the damn problem!" because "it's just a protocol" leads to this kind of bullshit fragmentation right here.

          Comment


          • #75
            Originally posted by Quackdoc View Post

            KDE is far more preformant then gnome is. Gnome stutters when opening a bloody notepad on lower end hardware.
            KDE definately has far less fancy desktop effects than gnome.

            otoh if you put it on decent hardware, those effects are.... fancy.

            for those willing to switch to X11 you can even screen record them, like this


            Comment


            • #76
              Originally posted by skeevy420 View Post

              It's also proof that RHEL is using Wayland to EEE people into GNOME. Instead of creating a shared system everyone can benefit from, they extend or propose to extend the Wayland protocol and only implement it in GNOME and Mutter so only they benefit.

              They get to show the world how great, altruistic, and open they are while that exact same action directly stifles and hampers their competition. It's brilliantly nefarious. And if anyone says anything people start repeating the "But, but, but it's only a protocol" mantra like that means something while the rest of are like, "No shit. It's just a protocol is the damn problem!" because "it's just a protocol" leads to this kind of bullshit fragmentation right here.
              I dont agree with this, the issue is that these extensions aren't being proposed and implemented in the wayland protocol. that's the issue gnome kde and sway go and do their own shit. Sway/wlroots at least uses wlr-protocols instead of some braindead dbus or under the hood protocol that only they are supposed to use. I don't agree that they should implement for other people, not being forced into protocols you disagree with is one of the massive benefits to wayland. (even if CSD has shown it to be a detriment too).

              Both KDE and sway are pretty decent at implementing protocols when they get added to the spec, it's when they arent added it becomes an issue

              Comment


              • #77
                Originally posted by skeevy420 View Post
                It's also proof that RHEL is using Wayland to EEE people into GNOME. Instead of creating a shared system everyone can benefit from, they extend or propose to extend the Wayland protocol and only implement it in GNOME and Mutter so only they benefit.

                They get to show the world how great, altruistic, and open they are while that exact same action directly stifles and hampers their competition. It's brilliantly nefarious. And if anyone says anything people start repeating the "But, but, but it's only a protocol" mantra like that means something while the rest of are like, "No shit. It's just a protocol is the damn problem!" because "it's just a protocol" leads to this kind of bullshit fragmentation right here.
                Amen.

                Comment


                • #78
                  Originally posted by Sonadow View Post
                  That's the problem with the compositor and not Wayland the protocol. Blame Gnome, Plasma and Sway for not getting it right even after a decade into Wayland.
                  What are you talking about? Any compositor-internal API is not Wayland. Your app can do whatever the hell it fucking wants. But to claim it's Wayland or Wayland-compatible, it needs to implement the Wayland protocol. Anything outside of this is not Wayland. You can create a Windows platform with all sorts of extra APIs you want, but they're not Windows' API in such case.

                  So yes this is why you can blame the god damn protocol. If it's so shit and crippled that it doesn't offer you a way to do something and you have to expose your own API for it, then it's its fault. It's as simple as that.

                  WTF is the point of a protocol if you make up your own APIs?

                  Comment


                  • #79
                    Originally posted by skeevy420 View Post

                    It's also proof that RHEL is using Wayland to EEE people into GNOME. Instead of creating a shared system everyone can benefit from, they extend or propose to extend the Wayland protocol and only implement it in GNOME and Mutter so only they benefit.
                    Well, it's like that since beginning. At least to some part. KDE always wanted to have common solutions, but Gnome didn't care and they were doing things on their own ignoring KDE. When comes to Wayland, Gnome had better support in the beginning (that's why I switched), but I think KDE will overtake them. Gnome/Red Hat/Whoever should understand KDE is not going to go away and it's as much as important as Gnome. It would be great to have common solutions for developers, so they can write once and don't have to care if their application is launched in KDE or Gnome. If that's already possible it would be nice if it was advertised at twodesktops.org etc.

                    Comment


                    • #80
                      So if you use KDE + AMD/Intel you are fine with PCSX2 on Wayland

                      If you use GNOME + Nvidia it is unusable

                      Comment

                      Working...
                      X