51–60 of 70 posts
Earlier quoted context omitted.
GP's question seems like it might be a common question. Would it make sense to add this to the readme?
Good point. I'll make a note to add some documentation to that effect. I didn't think of it originally because I didn't expect this much interest in my project.
Earlier quoted context omitted.
Buggier or not - it's too late to think X11 is the alternative. It's not. Wayland is going to get better for whatever is needed. X11 is absolutely not the way to go.
X11 was absolutely not the way to go since the day it was released on 15 September 1987, but that never stopped it.
There isn't anyone left standing to care for X11 development, only vocal users.
I updated my script for i3wm to toggle windows between scratchpad/active/start/stop:
https://gist.github.com/tkapias/0443d4930c1d7b520f4496e1ff39...
Earlier quoted context omitted.
It depends a lot on your desktop enviornment/window manager, distro, hardware, etc. I personally find Wayland works perfectly out of the box whereas X11 still to this day has issues with basic stuff like screen tearing that needs me to add a line to my xorg config file to enable the driver feature that stops screen tearing. (Note that every other display server has zero issues -- MacOS, Windows, Wayland, etc so the f…
What are you running when you experience screen tearing? I've literally never once encountered it in over 20 years of using X.
Sometimes adding a compositor like Compton helps, but you still see it
Earlier quoted context omitted.
It works. Therefore, it's viable. It's my computer. I decide what's "the way to go" or "viable" there. None of your business. No one is forcing you or anyone to use it. This is clearly a "I wrote it because it's useful for me, I put it online for whom it may concern"-type of project. You need to calm your tits and stop shitting all over people's hobby projects.
You can decide whatever you want. Being stuck with unsupported case (X11) you support yourself is "viable" as long as support yourself is something you can do.
Earlier quoted context omitted.
It's not like xdotool is so secure in the first place. X11 is one huge hole from that perspective. Anything can read anything and all your important input can be read by some other window anyway.
This is a totally different issue; Wayland gives up the ability to provide user-aid that prevents an obvious human error. This is not really a security issue, it is a usability issue that can just happen to allow a user to make a security slip-up. In exchange, Wayland gains… well, nothing really, the idea is that it’ll protect users from malicious programs peeking at other windows on their computer. But in that case…
Earlier quoted context omitted.
Makes perfect sense for it to be something that interacts with the compositor. So KWin does expose such API. But that's not part of Wayland itself or its protocols. Want to make it easy? Use KDE which cares about flexibility and write scripts for it. Otherwise - probably tough luck, not sure how much other compositors even care about such things.
Or I could just use X11, where this is a solved problem using a single API that works on arbitrary window managers / desktop environments. The only problem is people keep showing up to tell me that I need to stop using it and use their feature-poor alternative.
Earlier quoted context omitted.
Lol - it's "stuck up" to prefer software that works? If you want people to switch, it'd help to actually cover their use cases. Showing up to proclaim software "obsolete" when the supposed replacement literally doesn't support the features in use, then... what, claiming we're bad people for not contributing to Wayland? is the cultural part of why people don't like Wayland. (In a distant second place behind the techni…
Stuck up means they don't care to collaborate. If they don't, how would anyone know about their specific needs? Those who don't have this dinosaur mentality do work with Wayland developers and their needs are addressed faster. Others learn the hard way but also usually like to complain that "things don't work".
Or maybe it‘s because the compositor developers are not exactly concerned about ease of development. To quote a GNOME dev[0] about support for the aforementioned drm-leasing protocol:
> I honestly don't have a problem with forcing clients to implement the portal if they want to work on mutter.
I wouldn‘t blame the people who choose to simply not engage with that process, especially those who work on these things in their free time.
[0]: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2759
Earlier quoted context omitted.
> The question is "when?". Wayland is 15 years old, it already had a lot of time to "get better". So today, in most cases, I'd say X11 is still the way to go, it just works better. If you run more than one monitor with different DPI, Wayland is the only choice. If you want to do HDR, Wayland will be the only choice. > When Wayland will get better and apps start supporting Wayland more than they support X11, it will b…
X11 has supported mixed dpi from nearly the very beginning. http://wok.oblomov.eu/tecnologia/mixed-dpi-x11/
Earlier quoted context omitted.
This is a totally different issue; Wayland gives up the ability to provide user-aid that prevents an obvious human error. This is not really a security issue, it is a usability issue that can just happen to allow a user to make a security slip-up. In exchange, Wayland gains… well, nothing really, the idea is that it’ll protect users from malicious programs peeking at other windows on their computer. But in that case…
The idea is that to worry about security in something broken by design is a folly.