I desperately want to know what he thinks his worst idea is

I made a better solution in my post that works perfectly… and is better for me because it isn’t a script (I don’t like adding additional dotfiles) sorry for the unnecessary effort.

Do foss models really matter? I’m pro foss and think proprietary software should be banned but these weights are essentially a compiled program, we have no idea what they do

Test setting it in /etc/environment

Why not just switch to MPV?

yeah i’m doing this because i’m anal not because there’s a good reason to.

deleted by creator

Every single way that flatpak doesn’t integrate well into the OS is easily fixed with minimal effort.

I highly recommend fedora kiniote if stability is your goal always go immutable

Do you have any better suggestions?

The real reason for alacritty is that it’s my terminal emulator of choice and it needed to run “xclip -o | wl-copy” while in focus, or the clipboard won’t update properly.

I think they should use matrix

Oh it’s because the protocol forbids apps accessing the output of other apps without special support for it, so unless apps manually include support for Wayland, it will not work.

It’s no more special than what they had to do to support X…

With many apps that don’t even do anything related to screenshotting or overlays - like Guake - it still does not work.

Actually guake already works perfectly.

So most of my usual workflow is just broken by Wayland, productivity utterly shattered by some middleware crap and for what? Why?

Security, proper rendering, mixed refresh rate displays, color management, HDR, no more insane hacks, I could go on. Also, you can’t actually name a way in which your productivity is actually affected.

Why? Why must the graphical protocol of all things break random software incl. accessibility, overlays etc.? No other OS has ever had this issue. No other OS finds it a security concern to allow apps to see other apps.

Other OS’s DO have this issue, you have no idea the things macos has enforced, and we have backwards compatibility using xwayland, being forced to update to a new standard IS normal for operating systems, linux just delayed it for as long as possible. The problems with X11 are MUCH more vast than the problems other operating systems have.

The only reason Wayland does is because it’s just terribly designed from its very conception despite the constant warnings from other Devs and users.

Name one actual problem with the design.

Oh and then there’s the Nvidia driver support…

That’s 100% nvidia’s fault and almost completely resolved

Look at what they did with PulseAudio - now that’s the right way to do it, users don’t even know the difference except suddenly everything just works a bit better.

That wouldn’t have worked with X11 at all, because x11 is so fundamentally broken that making a successor to X is completely actually impossible, there’s a reason all the X11 devs which you believe are so brilliant for making x11 decided to switch to developing wayland, and decided that what you want is actually completely impossible while making an actually well designed desktop. Please actually look into the history of this. The people who actually know how X11 works, refuse to work on it, and for very good reason. If what you were saying was true, there would be an X12 project in the works… but there is not, because it is fundamentally awful.

Ye I know that, this isn’t the own you think it is as the GNOME Devs lost their mind long ago in many other ways as well.

It’s also the default on KDE now, also, I don’t understand why you seem to believe they should’ve rushed this out, what they did was correct, x11 wasn’t going anywhere, you can still use X11, the point of wayland was to redesign things from the ground up to be as perfect as possible, and they’re (slowly) achieving exactly that.

Use x11 if any of your usecases aren’t met by wayland, it’s not like they deleted it. But wayland is the future. They were right to make it partially non-backwards compatible, they needed to restart from scratch.

You’re looking for Hyprland!

If you don’t know, the fix for that is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967

Debian has implemented it. Screenshotting has worked perfectly for years, maybe half a decade at this point.

edit: I just checked, screenshotting has been working since 2015 https://github.com/swaywm/sway/issues/1

Debian has been using wayland by default on gnome since 2019.

This is an impressive level of confidence for someone who has no idea what they’re talking about.

Also, seeing as you’re the guy who doesn’t even have accessibility problems, that means you have… no problems.

Remind me again, what is so bad about wayland?

It’s better in just about every way, objectively, I don’t really know what you’re talking about here.

You have one issue, accessibility, what other flaws do you see with the wayland protocol?

Why do you think it is that none of the people who worked on the X protocol would agree with you that wayland is worse in any way?

What specifically do you think is worse?

Why do you think literally every single desktop project is switching to wayland with no plans of implementing a different protocol, ever?

I feel like your version of reality is completely imaginary.

here’s some things that will never be fixable in x.org

1. Recording all of your activity is extremely easy for a malicious program
2. Multiple displays with mixed refresh rates that aren’t clean multiples of eachother
3. Color management/hdr
4. Rendering (try resizing something and notice all the garbled nonsense)
5. Proper scaling support

There’s more.

I’ve developed an install alias that automatically configure a wide variety of things really easily for arch, I had a bunch of people use my setup and logged the usage of each different keybind, then sorted them by most used and put those on the strongest fingers

I’ve spent more than a few hundred hours configuring stuff, you can check it out here if you want:

https://gitlab.com/that1communist/dotfiles/

It is on hyprland and kde, if that helps

Does input-leap help?