Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PCSX2 Disables Wayland Support

github.com

Post reply on HN
Print view View original

111–120 of 208 posts

Re: PCSX2 Disables Wayland Support

#111

Post by MindSpunk »

Gigachad wrote: post #44
rowanG077 wrote: post #37

Earlier quoted context omitted.

Xwayland is instantly recognizable as shitty due to fractional scaling. Which almost everyone with a modern laptop uses.

I might not be up to date on this, but does fractional scaling work at all on Linux under any setup? Last I checked GTK just flat out didn't support it or something.

KDE supports fractional scaling. GTK doesn't and as a result neither does GNOME. There's hacks in gnome to work around this by faking it with downscaled integer scaling (render at 2x, squash into 1.5x) but it never provided a good experience for me.

Re: PCSX2 Disables Wayland Support

#112

Post by helij »

uneekname wrote: post #86
anaisbetts wrote: post #42

GNOME as a platform (and by extension, all of their associated projects which unfortunately includes the Wayland protocol) has such a bizarre worldview - it's like they think they can treat the Desktop OS, with all of its user expectations and existing working software, and remake it as a bigger iPadOS, to no one's actual benefit. What do I get in return for having to give up all of these things that used to work? It…

It's cool if GNOME doesn't work well for you, but for me it's near-perfect. For sure it's rough around the edges, but what isn't? GNOME helps me get work done, stays out of my way until I need it, etc. I see so much general hate towards GNOME on HN, and it's really annoying. If it doesn't work for you, great, I'd like to hear why. But saying it's "strictly downsides" simply isn't true, nor productive.

Same here, everything just works for me on base Debian and Fedora installs.

Re: PCSX2 Disables Wayland Support

#113

Post by djbusby »

nolist_policy wrote: post #29
londons_explore wrote: post #8

Earlier quoted context omitted.

The vast majority of users today run a hybrid of Wayland and XWayland... Getting the worst of both worlds, and extra bugs to go on top...

That is not true though, XWayland is better maintained than native Xorg. It is here to stay for backwards compatibility. Disclaimer: I run ChromeOS and Wayland just works.

Oh, I've got a Chromebook; didn't know it was all Wayland.

I'm thinking that it "just works" there because G has more resources to patch all the needed features. More resources than KDE or Gnome or others have available.

Re: PCSX2 Disables Wayland Support

#114

Post by LtWorf »

hashworks wrote: post #74
LtWorf wrote: post #59

Earlier quoted context omitted.

Why learn about wayland and figure out how to fix things (and then probably have gnome developers never ever accept your fix) when you can just switch to Xorg in 3 seconds?

There are good reasons to switch to Wayland. Features, security Standards and it being in active development are some of them. Of course no one has to use / switch to anything, but reaching a critical mass of users would be helpful in the long term.

You CAN use multiple sub-instances of Xorg for security… Nobody does it but firejail supports it.

Re: PCSX2 Disables Wayland Support

#115

Post by LtWorf »

Arnavion wrote: post #96
LtWorf wrote: post #57

Earlier quoted context omitted.

> does a good job with what it's supposed to do. And anything that people used to do on X11, they are told by zealots that they are wrong and aren't supposed to do that. For example: Not losing all the work every time your windows manager crashes remapping keys Use xinput to change parameters of their input devices (libinput dropped most configuration options present with evdev) Global shortcuts tunnelling over ssh

>Not losing all the work every time your windows manager crashes https://news.ycombinator.com/item?id=37509703 >remapping keys >Use xinput to change parameters of their input devices (libinput dropped most configuration options present with evdev) Up to the compositor. >Global shortcuts Also up to the compositor. Was added to xdp in https://github.com/flatpak/xdg-desktop-portal/blob/main/data... so it's up to the com…

> Up to the compositor.

> Also up to the compositor.

Exactly my point! Right there. Thanks.

Re: PCSX2 Disables Wayland Support

#116

Post by LtWorf »

antod wrote: post #108
Gigachad wrote: post #94

Earlier quoted context omitted.

I’ve used Linux for over 10 years and I don’t even know what an xorg config file is. I suspect most users don’t. I wouldn’t expect my desktop environment to require any config.

That stands to reason - the last time I had to edit xorg configs was probably over 15yrs ago getting multi monitor working before xrandr. Since 2005ish, xorg seemed to be able to happily autoconfigure itself.

I didn't mean /etc stuff, I mean more like Xmodmap, .XCompose… the sort of things americans don't use and are completely unaware of.

But I personally speak 5 languages (with very different levels) and writing gets a bit complicated.

Re: PCSX2 Disables Wayland Support

#117

Post by Arnavion »

jwells89 wrote: post #107
wtallis wrote: post #61

Earlier quoted context omitted.

Why can't ImGui applications do multiple windows while leaving the positioning up to somebody else (the user or their window manager)?

Imagine a program that utilizes several separate windows for palettes. If the program has no way to specify where to place those palettes, the user is going to be presented with a ton of palettes piled on top of their document window and that they’ll have to sort that out themselves, rather than a neatly organized immediately usable workspace. That’s not really an acceptable user experience no matter how you slice it…

>Imagine a program that utilizes several separate windows for palettes.

One way this can work is: When the program starts up on first install with a brand new config, all those palettes are part of the program window. Then as the user decides to undock them one by one, they are removed from the main program window and a new window is drawn containing that palette. So the user isn't presented with "a ton of palettes"; they get them one at a time and can move them as they wish.

The rest of that (maintaining their position next to the main window, restoring them when the application is restarted) would be solved by a protocol that allowed relative positioning, which was already suggested in the wayland-protocols MR discussion.

>it can be useful to have functionality that lets the user designate a screen for a particular function (for instance, putting sliders and knobs for audio production software on a touchscreen)

This can already work today if the compositor provides a way to do it, as long as the application tags such a window with some unique `app_id` or `title`. For example in sway the user can write config rules to match windows based on such criteria and run position etc commands on them. I assume KDE also has something like this because I remember it having a way to match windows using X properties in the KDE 4 days.

Re: PCSX2 Disables Wayland Support

#118

Post by LtWorf »

saghm wrote: post #67
LtWorf wrote: post #48

Earlier quoted context omitted.

Works flawlessly if you've never edited a Xorg config file… if you did, there is no way to keep using the same configuration

Not ever having to touch Xorg config files to get things working is pretty big advantage to me at least.

So let me know how do you write 5 languages properly…

Re: PCSX2 Disables Wayland Support

#119

Post by LtWorf »

Gigachad wrote: post #94
LtWorf wrote: post #48

Earlier quoted context omitted.

Works flawlessly if you've never edited a Xorg config file… if you did, there is no way to keep using the same configuration

I’ve used Linux for over 10 years and I don’t even know what an xorg config file is. I suspect most users don’t. I wouldn’t expect my desktop environment to require any config.

Try to define custom XComposeKey sequences, so that you can write math symbols or greek letters and you will find out immediately.

For example I can write ∀ x ∈ ℕ: x > 1 → x² > 1, but not in wayland.

Re: PCSX2 Disables Wayland Support

#120

Post by [deleted] »

k8svet wrote: post #76
Zambyte wrote: post #65

Earlier quoted context omitted.

I think it's more interesting how Wayland has worked fine for me on AMD, Intel, and Nvidia for the last 4 years on my personal machines and work machines, and yet here we are still talking about if it works or not.

If you pay enough attention you'll start to notice the same users names across comments and threads. Hallmarked by ignoring any replies, repeating their pet peeve, repeating experiences from years ago as if they were recent re-tries, and ignoring the laundry list of features possible with Wayland that are impossible or declared as never happening with X11. I made the mistake, I clicked the thread, and even replied. M…

[deleted]
Post reply on HN