341–350 of 502 posts
For me the graphics server is tied to my favourite environments for lightweight use: Xfce and Lxde both use only X11. Also, I still cannot understand why a server has to depend on the installed graphics card as the driver stays in between and should abstract and make the software hardware-agnostic.
Earlier quoted context omitted.
Trying to be funny, I see.
Better than trying to make a point and failing to make it. And if I didn't, at least I tried to be funny as that counts for something, your comment is just noise.
Unfortunely Valve failed to make native Linux gaming a reality, not even game studios targeting Android NDK bother, which has the same 3D and audio APIs as GNU/Linux.
Earlier quoted context omitted.
Did perl5 to perl6 actually happen? I feel like perl mostly fell out of favor along the way.
Disclosure: I'm not intimately familiar with all this. I think Perl5 was originally planned to be replaced by Perl6. Then Perl6 took much longer than anyone expected, and kinda ended up in a different place. Perl5 was re-anointed as the once-and-future Perl, and what had been Perl6 became Raku. If I remember correctly, somewhere in the middle of all that there was talk of running Python (and other languages) on the n…
Disclaimer: I don't have any skin in this game, I was fine with X11 and I am fine with Wayland, and I actually think it's nice to have both (and more, like Xlibre I think?). I understand complaints about systemd, I don't understand the complaints about Wayland. This whole article sounds like a big rant and doesn't seem to bring much information. > I also don't care for the "security" argument when parts of the core r…
> Who is forced to use it? Anyone who wants to continue using a modern, actively-developed desktop environment. GNOME has dropped X11; KDE has announced the transition. I would consider being told "use Wayland, or find a different desktop environment" being forced, even though nobody has actually put a gun to my head. I have managed to make Wayland work for me, but only by patching away the hardcoded gestures. I also…
Yes, and I also think it's important to focus on that part in particular: X11 is not a feature, it's not a user story, it's an implementation detail of the desktop environment / window manager.
There are certainly historical architectural choices that imply many aspects of what X11 can or can't do for the user, likewise with desktops' implementation of the Wayland protocol. The differences between these approaches is real, and substantial.
But in the end, X11 is not a cause unto its own. It's a component in service of the user experience at large. People criticize the removal of X11 support either because their use cases have been affected in some inconvenient way, or because they're afraid of future consequences one way or another.
It's important that desktop environments work on providing the features/UX/quality that users need and expect. It's also important that users tell their DE developers what their needs are, in terms of what problems they are trying to solve, not in terms of which components to use underneath. Choice of component stack is a developer issue and should remain this way.
In the end, the DEs/WMs that solve their users' problems to a high degree of satisfaction are the ones who will retain and gain the most users. Approaches will differ across the Linux desktop space regarding what problems to solve specifically, which problems to prioritize, and how best to implement solutions for them. Dependencies like X11 shape the ultimate user experience one way or another, in terms of features, constraints, development effort, and continuity.
And so do many other implementation choices that need to be made or revised along the way. Ideally most users will end up with DEs/WMs whose development philosophy is aligned with their personal priorities. Friendly bug reporters can help out with the awareness part at least :)
Which ultimately is fine, this reflects the focus of the people who have the skills and opportunities to contribute and is unlikely to change any time soon.
That is somewhat unfortunate for some but ultimately if you’re asking people to work for free you can’t be too picky on what they choose to work on.
Disclaimer: I don't have any skin in this game, I was fine with X11 and I am fine with Wayland, and I actually think it's nice to have both (and more, like Xlibre I think?). I understand complaints about systemd, I don't understand the complaints about Wayland. This whole article sounds like a big rant and doesn't seem to bring much information. > I also don't care for the "security" argument when parts of the core r…
The last time a distro tried to sell me on it, it left me unable to drag/drop browser tabs to reorder them (a fundamental part of my daily workflow). Thankfully, Mint still has the option to use X11 so reverting was trivial. That won't always be the case because...
> Who is forced to use it? Just use X11, as you said (many times) you do already.
Which, like avoiding systemd, is becoming increasingly difficult as distributions prematurely switch. Like when some Linux distros made KDE4 the default (~20 years ago) before most graphics cards could actually handle KDE4's requirements. Switching distros after years, even decades, of use is not as trivial as distro-hoppers who swap out their distro every three weeks might like to think. Lots of know-how and muscle memory gets lost in the transition, both of which have to be rebuilt.
In short, this reads like a mix of valid historical pain points and outdated assumptions. The post frames Wayland security as “you can’t do anything,” but that’s a misunderstanding. Even under X11, any app can log keystrokes, read window contents, and inject input into other apps. Wayland flips this to isolation-by-default: explicit portals/APIs for screen capture, input, etc. Moreover, the performance argument is we…
The problem is old (and even not so old) apps don't expose those APIs so interactions like UI automation on Wayland is limited, if not impossible. I'd love to grant a specific permission just for selected GUI apps, but I can't because they don't support it.
There's a reason why RPA software on Wayland is limited to web apps inside a browser. Or something extremely janky like taking screenshots of the entire desktop and doing OCR. But then you can't interact with unfocused apps.
> Regardless, I simply don’t give a shit about you anymore. > > We’ve sacrificed our spare time to build this for you for free. If you turn around and harass us based on some utterly nonsensical conspiracy theories, then you’re a fucking asshole.
You haven't sacrificed your spare time. You've done a thing you wanted to do, and had a tantrum when it turned out it had consequences.
You want to do a thing, fine, but the moment it's forced on people you have taken on responsibility, whether that was what you wanted or not. Grow up.
> At this point I consider Wayland to be a fun toy built entirely to pacify developers tired of working on a finished legacy project
Pretty much this.
The major comitters and maintainers of X decided it was a lost cause and unfixable. Were they just supposed to keep working on the massive pile of hacks they felt needed abandoning? They did what they thought was best. You hate it. Fine. Do you think things would be better if they kept working on the unfixable mess? I trust them to know what was going on better than random commenters.
His pain is that it's been 17 years and some basic core functionality is either still broken or entirely missing. It's not my expertise so I don't know if it could have been planned any better, but 17 years and _basics_ still being broken doesn't sound great.
Earlier quoted context omitted.
My experience lately has been similar. Most things work well now. But, I think the article has some valid points about how long it's taken to get even this far. And it just kinda sucks that some things are still broken or don't have alternatives (the #1 thing I miss right now is Barrier (Synergy) for using my macbook from my linux desktop). HDR gaming on linux is possible thanks to Valve but it's still nowhere near a…
> the #1 thing I miss right now is Barrier (Synergy) for using my macbook from my linux desktop) It's admittedly tough to keep up with all of the forks that have happened, but the current iteration, Input Leap, has worked for this for me for years now https://github.com/input-leap/input-leap