If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
PCSX2 Emulator Disables Wayland Support By Default
Wayland is broken by design in many ways.
But sadly it is the best we currently have and will have for the next two decades.
Repeating a claim on a subject a person knows very little failed to make it right. The job is assigned to compositors for handling applications while Wayland protocol is designed for minimal libraries as possible in mind.
Whatever your complaints are, Gnome is still the most performant and usable Wayland desktop environment to date compared to the other two.
That statement feels outdated. GNOME lags behind with features like:
- VRR
- Tearing control
- DRM leasing (for VR headsets)
- SSDs (yes, that is actually missing feature and saying it’s more of a paradigm and the proper direction is denying reality where 3rd party toolkits and apps are forced to draw their own borders and end up being borderless or ugly/buggy/inconsistent)
- Crash recovery (and it’s not so stable after all)
That statement feels outdated. GNOME lags behind with features like:
- VRR
- Tearing control
- DRM leasing (for VR headsets)
- SSDs (yes, that is actually missing feature and saying it’s more of a paradigm and the proper direction is denying reality where 3rd party toolkits and apps are forced to draw their own borders and end up being borderless or ugly/buggy/inconsistent)
- Crash recovery (and it’s not so stable after all)
Its more that gnome were the first to give up on wayland and concentrate on just doing DE stuff rather than wasting precious developer time on functionality all DEs have had for 30 years.
Plasma 5 was released in 2014...
The only reason gnome still have wayland as a default at this point is changing that would go down with the people sponsoring them about as well as announcing your first born is going to study advanced physics in Moscow during a dinner party hosted by Zelensky.
Last edited by mSparks; 27 November 2023, 01:49 PM.
HAHA doubling down on lunacy when i'm calling out your incompetence is all you got?
highly intelligent rational decomposition of the attack the messenger not the message metaphoric argumentation like this really brightens up my day too.
nothing funnier than watching a microsoftie learn android and chromeos are Linux distributions tbh.
Watching them come to terms with winblows being barely as relevant to modern computing as wayland is really as good as it gets.
That is not a compliment btw. I'm laughing at you not with you.
Last edited by mSparks; 27 November 2023, 03:07 PM.
He is mostly complaining about the Qt implementation of CSD. Actually his language sounds not very professional too.
He is just an emulator code-monkey. And honestly, PCSX2 is one of the worst emulators ever made. it took them decades to finally reach an acceptable state. Compare this to Dolphin, for example.... I am not surprised its devs act this way.
Arguably, GTK is the "platform API" for GNOME and gives applications decorations, like USER32.DLL does on Windows and Cocoa does on macOS. But, on the side point, these platforms have the benefit that every application has to link against the system toolkits in order to run, it isn't optional.
Glad we agree. I write applications for Linux+Wayland, not GNOME. Until they come into compliance with the Linux+Wayland standard that KDE, wlroots, etc. implement and honor requests via the decoration protocol, I consider GNOME to be an unsupported out-of-spec platform I'm not trying to target which just happens to implement enough of the API to run my creations badly.
Join the "please turn to your community for support" queue with Haiku and OpenBSD users over there, please.
ApplicationWindow is part of GTK which is what GNOME is built on. It's the platform.
Yeah, and if the GNOME platform wants to implement an incomplete subset of the Linux+Wayland platform that's missing the extension for server-side window decorations, that's their problem and I will direct users of my creations to them for support.
I target the de facto standard Linux+Wayland platform as implemented by every compositor of note except GNOME. Hell, GNOME/X11 is an "if I feel like it today"-supported platform because GNOME Shell is so sluggish in VirtualBox and I haven't had the time and motivation to play around with a QEMU/KVM-based alternative.
Repeating a claim on a subject a person knows very little failed to make it right. The job is assigned to compositors for handling applications while Wayland protocol is designed for minimal libraries as possible in mind.
this is a distinction without a point. this is about the collection wayland cabal that has done everything possible to ensure that wayland adoption is stalled. through gnomes absurd views of what a desktop should be, to the non-standardization of many basic functions.
you can argue all day long that it's not a wayland issue but a compositor issue ( or a gnome issue or a systemd issue or a dbus issue), but that's missing the forest for the trees. it's a desktop issue, and developers should be able to write apps that just work on the desktop. since wayland brought on this mess, and the wayland community has yet to get their act together, then wayland is the name we'll use for this issue.
if kde/gnome would sort out their differences, and just say yes, we're committed to supporting this baseline of capabilities consistently across wayland/wayland extensions, libseat, dbus, systemd, xdg-portals. and just align their roadmap around that, that would show they care enough about developers.
at the moment, you know gnome cabal thinks CSD is a holy war, that they will never admit the cost to wayland adoption, let alone change their mind.
Last edited by fitzie; 27 November 2023, 03:24 PM.
Comment