This whole argument ignores xwayland and the fact that new features are added as a standard of Wayland literally every day.

For as long as xwayland is supported you can use your old apps. Wayland actually supports different window icons for multi window apps. But Wayland has always supported window icons, kde just had an annoying bug they finally fixed. Chromium and electron apps kinda just didn’t support window icons very well in wayland for a while.

For accessibility, it’s been broken on Linux for literally years but there’s an active effort to make it better and more universal than it ever could have been on x11. The effort of building a fully featured accessibility stack is being led by the gnome team with help from the free desktop organization and kde.

This is my last response, this conversation isn’t going anywhere anyway. I’m not the one transitioning the Linux world to Wayland, I don’t see why you could blame me for it anyhow.

Your arguments kinda weak, no offense. I do have a solution for you though. If you want to stick with a version of Linux that’s guaranteed to support xorg for eight years, I’d recommend Rocky linux! When that reaches EOL I guess you could just stay on it.

Enterprise plans on being fully switched over to Wayland by the next major version. You won’t be able to install xorg on redhat for example. The biggest contributors to xorg(Enterprise) are going to shift focus to xwayland to support legacy software on wayland.

Besides it’s exciting finally catching up to truly hardware accelerated desktops like Mac OS 10.0 and windows vista. At its heart xorg is a purely single threaded software accelerated bitmap based windowing system from 84. They’ve had to rewrite small but incredibly complex chunks of the code just to try to keep up with the modern world. Just look at the history of 3D acceleration in x11.

Your free to give it a good go though! The very same team that actively maintained xorg threw in the towel ten years ago when they diverted resources towards a new windowing protocol and they’re not going back.

If developers drop off there’s not much we can do. It’ll eventually have to be removed or become a bigger security risk than developers say it is already.

Support on the x server itself has dropped off precipitously since Wayland hit the mainstream and most small x11 DEs are trying to build off of WM like wayfire or wlroots.

I don’t think kde plasma was the only one. Anyway, it just feels natural for xwayland to stop pushing for feature parody and for focus to switch over to Wayland after a while.

The biggest target for developers is the Ubuntu/Debian platform so their switch to Wayland should motivate other projects and paid applications to at least take notice.

New projects will try to support both but typically will focus more on Wayland. There’s already an unintentional incentive to partially support xdg protocols Wayland relies on thanks to flatpak.

They’re already starting to go that way, in a couple years Linux mint is even going to support Wayland. Ubuntu and fedora has already defaulted to Wayland. Fedora is actually deprecating xorg in a few releases. Budgie wants to have full support next year.

There isn’t much more than the testing they already have to do every release. Infact not having to support legacy code will free up resources for the whole Linux community as well as cutting the time in half for validating packages on distros. Every package that runs on xorg also runs on wayland, they have to test both.

Granted some have custom tools they’ll be working on but it’s going to be a while before every major DE supports Wayland. I’m curious, you think the distros have to implement their own version of Wayland?

Once the desktops switch to Wayland and all distros ship with Wayland by default, support should slow.

Ideally, developers stop improving xwayland over time and go into maintenance mode for a bit. Once it goes into maintenance mode, developers should naturally fall off as it winds down.

If every desktop makes a very public announcement about the xwayland protocol being put into maintenance mode, actively supported apps should switch over. It’s up to the public how long they want to keep maintaining xwayland (open source etc).

For a second there I thought you were hating on the guy.

Yeah, they could puppet the chrome company if the courts don’t keep a close eye on it. Basically there’s a good chance it would be another Firefox but with way more influence.

Isn’t it already licensed under permissive Apache v2? Anyone can fork and carry on the project without the permission of Google, every manufacturer already does as a result of the license.

I don’t know, they’re just security measures you can take. Maybe some personal preference thing. I don’t bother with the app guard thing and SELinux is pretty annoying with my Nvidia graphics card but a firewall is something I always setup.

Firewalled for limiting untrustworthy connections to the computer(public networks, hotels, even work).

apparmor for protecting the kernel and controlling file access to applications. SELinux is also a good option but if you need to load kernel modules, it can take a few minutes to sign and register it. It is automated on redhat systems though.

Other than that, do your research and don’t run random scripts and install random apps.

Oui oui

I thought it was funny,

Honestly, if your programming your ECU or something. I wouldn’t risk potentially bricking your car. It is a tool after all, something like how I prefer mikita over Milwaukee but I’ll use it to get the job done if needed.

Edit: ECU software can be a little finicky. Jayztwocents built a PC for his mechanic friend and the application refused to start because it wasn’t an Intel CPU.

My household is a Microsoft free environment. There is no place for the royal we in this conversation.

😄I don’t want packages I want programs. That’s like a Mac user saying I don’t want programs I want applications. Booting up a Mac and saying where’s my god dam exe, why doesn’t anything work.

No offense it’s just funny.

Unless it’s a company, good luc…

Hay, how would you like writing documentation for all these open source projects? We would be ever greatful, you could even put your name in the credits!

The dankest depths of archlinux wiki. Written by a guy so far gone, so war harden by reading through source code and poorly written technical documentation, ancient forums, leaving no stone unturned. A task so twisted it drives most men crazy.

1% of arch users will ever need this wiki and few have gone through this Herculean task. For them, the first draft is enough, it’s all you can ask of a mind so twisted and broken. Alas it’s as unreadable as the source code and as hard to understand as the forum post from 2009.

I do wish there were more native apps but alternatives to electron is always a good thing in my book.

Except for Microsoft, Microsoft can stop pretending their solution is demonstrably different from electron and chromium.

Neat!