311–320 of 892 posts
Earlier quoted context omitted.
Hell, Emacs doesn't work in Wayland.
That's not strictly correct. Give the `feature/pgtk` branch from upstream a try, `make` it yourself unless your distro has a binary for it -- that (`make`'d myself) worked for me on Void Linux. There are also a few forks on GitHub with native wayland patches out there too if `feature/pgtk` doesn't.
> In the case of Wayland, the “vague authority” are a bunch of volunteers who have devoted tens of thousands of hours of their free time towards making free shit for you. That does not mean anyone is under an obligation to like it. > Maybe Wayland doesn’t work for your precious use-case. More likely, it does work, and you swallowed some propaganda based on an assumption which might have been correct 7 years ago. If y…
> I can certainly understand the frustration at having to deal with a community that gets annoyed at anything that changes simply because they're already so used to the garbage pile they have that they now hold the delusion that it's actually not garbage. It's not just the FOSS community, look at how non technical people react every time gmail, outlook or excel makes a tiny change to the UI (not to mention big ones).…
Honest question by someone who wants to try out wayland, do steam, gog games, and wine games work on wayland well? What about things like obs?
Earlier quoted context omitted.
I'm beating a dead horse at this point, but there's no such thing as "switching to Wayland". What most people mean when they "switch to Wayland" is that they're switching from Gnome on X11 to a "pure Gnome" stack that uses Wayland and a bunch of other Freedesktop standards for interopability. There is absolutely no code from the "Wayland project" running there, because the Wayland implementation is Gnome's own (it's…
It is actually one of the big, unfixable, conceptual problems of Wayland that all the effort is duplicated in each compositor. The Wayland concept pushes out most of the work to the DEs. That of course will result in tons of predictable inconsistency, incompatibility, bugs, delays, consolidations and general pain. Wayland devs are then generally in the lazy "worksforme, use sway (or whatever)" position while the user…
This is not something conceptual about Wayland, or intrinsic to it. Any display protocol can have multiple client/server implementations. It just so happens that most of the free desktop standardized around the X.org implementation for X11, but even for X11 there were multiple client and server implementations.
The second thing is that software duplication efforts have a well known, tried and tested solution: implement the duplicated effort in shared implementations or libraries [1] !
The thing I find hard to wrap my head around is that this complaint is given in a community that usually champions protocol-over-implementations and diversity of implementations. The people actually making a difference on the Linux desktop are damned if they do and they're damned if they don't.
Earlier quoted context omitted.
> I've been down this road a lot with FOSS software: "I don't use it because it doesn't do what I need", "sure it does!", "no, it really doesn't", "well you don't need that anyway!"... Just recently (I was on a Fedora box temporarily) I was trying to figure out how to get Nautilus to stop starting a search whenever I typed something, and instead highlight the nearest match in the current directory, y'know, like prett…
> I don't understand how that gives you dictatorial power over 100s of users who don't like the changes you've made. It doesn't - you are completely free to roll back those changes, or make different changes of your own.
Maybe.
I think the discussion should happen.
Because I don't think "I wrote it, if you don't like it, you write it" is a 100% defense to hordes of upset users.
I’m using a Dell UP2718Q (3840x2160, 144dpi, 60Hz) and a Fujitsu Siemens P17-2 (1024x1280, 96dpi, 75Hz) side by side, and without Wayland this setup isn’t even possible to get working properly. Sadly, KDE still doesn’t support it nicely under Wayland (so I moved to Ubuntu Budgie), but under X11 it’s entirely impossible to run it properly, as except for Qt nothing supports mixed DPI, or mixed refresh rates properly. O…
And yet on every other OS, users can take screenshots and use virtual keyboards... It's not because X's security model is broken that the solution is 'we'll just remove that functionality'.
Wayland allows the same as well. It’s just an include/exclude list for such APIs, so you can actually limit which programs can access what.
Under X11, jailing GUI apps is entirely useless as there is no actual security boundary. Under wayland, you as user are in control and can define whether spectacle should be able to take screenshots (sure) and whether myflashlight-flatpak should be able to access all input events and take screenshots (probably not).
Earlier quoted context omitted.
I'm pretty sure that it's a bug in Chrome / Chromium since other applications are just fine even when Chrome is being dog slow.
If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
Earlier quoted context omitted.
> I've been down this road a lot with FOSS software: "I don't use it because it doesn't do what I need", "sure it does!", "no, it really doesn't", "well you don't need that anyway!"... Just recently (I was on a Fedora box temporarily) I was trying to figure out how to get Nautilus to stop starting a search whenever I typed something, and instead highlight the nearest match in the current directory, y'know, like prett…
> I don't understand how that gives you dictatorial power over 100s of users who don't like the changes you've made. The option always remains to change it yourself or stop using it. It's not as if it's bound to the hardware (Apple) or shipped with the machine (Windows). It's not a SaaS that may vapourise or change underneath you. There's no way to force consensus in situations like this. The best you can do is force…
If I changed every bit of software I dislike, I would have no time left for my actual job. Yeah, I get it, these volunteers found the time to work on this one project and therefore get more of a say about what changes will be made, but you know what? They also have to use other software, and they would not have time to work on something like Gnome if they were busy making changes to Wayland or the Kernel or whatever else.
Worse, in my experience, Gnome developers will turn down patches that do not align with their ideas about how things should work. I have had it happen to me, I have seen it happen to others -- even when we find time to change something, we cannot commit to maintaining our own private fork, and dealing with merge after merge or trying to keep up with a project that has as much activity as Gnome or Wayland. Obviously some patches need to be rejected, but in the case of Gnome I have found that rejection often comes down to their notorious "less configurability is better" attitude.
As for stopping using it, how does that work with critical packages like systemd? At some point you wind up having to ditch an entire distribution, with all its infrastructure and maintainers, just to get one use case to work. In some cases you are left with a choice between a project that has the features you need but has received no updates (including security updates) in years, or a project that does not have the features you need but is actively maintained. More often than not people will just give up on their use case, which in some cases means giving up on open source software entirely since that use case was the reason they were using open source in the first place. Some might think that is fine, users have the freedom to choose what software to run, but the fact is that fewer users means fewer contributors (including many people who make only the small but very important contribution of reporting bugs) and a less robust open source ecosystem.
Earlier quoted context omitted.
I'm pretty sure that it's a bug in Chrome / Chromium since other applications are just fine even when Chrome is being dog slow.
If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?