Wayland is not providing support, that’s individual compositors providing support due to the lwayland’s lack of support. The idea that Wayland doesn’t support screen casting is a myth. The feature to use screen casting exists, people just aren’t updating apps to use it. Instead the application must request screen casting rights from the compositor. But IMHO ignoring user input is regressive and it’s something that we, the linux community at large, need to work on. If they do it more securely, that’d be fantastic. I’m criticizing wayland on it’s own merits. You are welcome to criticize X windows all day long but that’s a straw man because I’m not defending the X implimentation. In X, any app can spy on any other application, which makes it easier to make a screen recording application, but absolutely terrible for security. Wayland didn’t turn their back against common use cases. Sure, waylands has it warts and all but 5 years from now, it’ll simply work.ĥ years from now Wayland might work, but if it does they’ll just break something else (networking? file permissions? USB devices? scheduler? who knows) and it’ll be the same old “In theory this shiny new bauble is technically better than the rusty old bauble, so we aren’t going to bother with any kind of migration plan or attempting to achieve consensus between distros, and then we’re going to roll it out before it’s ready while ignoring any/all of the pain that the transition causes users and developers”. The continual breakage (that alienates users) also causes fragmentation as different distros go in different ways and this causes extra bloat (more layers of libraries, etc to hide the differences) and divides developer efforts so rather than everyone (developers, distro maintainers, documentation writers, etc) working together to make one OS awesome they’re all working against each other to create (and continue) a “divided we fall” situation. It’s very hard to recommend linux to average joes when we still have these sorts of breakages. IMHO it’s worse that they know they’re breaking things and they’re intentionally not taking responsibility.ĭeploying wayland as default with missing features is a consequential decision that will either justify our platform’s widespread reputation in amateur circles of being too difficult and not being ready for general usage versus a platform that is serious about taking on user needs and taking steps to ensure things just work. But in this case we can’t pretend these problems weren’t anticipated, they’ve already had several years to fix them and it’s still not done. Some amount of issues are to be expected with a new rollout, you deal with the bug reports as best you can. I certainly hope all the features will simply work in 5 years, but in the meantime what about the breakages now? Sure, waylands has it warths and all but 5 years from now, it’ll simply work. Pulse audio was a good example of a badly managed rollout that eventually got fixed but in the meantime left some people with broken setups. Gnome3 didn’t break anything for me, but alas it turned me off of Gnome Desktop (non-technical preference). Some were non-events, but others were very “noticed”, haha. That’s a diverse collection and not all were equally received. The same was said about GNOME 2, GNOME 3, KDE 3, KDE 4, PulseAudio, Linux kernel v2.6 and more or less, any other major piece of software we use daily without even taking notice. The same was said about Xorg, ~15 years ago, and yet, I’m running a business using Linux (both servers and desktops). This is like buying a Mac and complaining your Windows applications don’t work. If you need the functionality that X.org delivers, then you shouldn’t be using Wayland. I’ll save you a read and summarise the ‘article’ so you can do something more productive, like I don’t know, cleaning your floors with a toothpick or something: “my tools and components written specifically for X and its APIs do not work under Wayland, therefore Wayland is garbage and shit”. Or force more Red Hat/Gnome components (glib, Portals, Pipewire) on everyone! DO NOT INSTALL WAYLAND! Let Wayland not destroy everything and then have other people fix the damage it caused. And usually it stays broken, because the Wayland folks only seem to care about Gnome, and alienating everyone else in the process. Wayland solves no issues I have but breaks almost everything I need. Hence, if you are interested in existing applications to “just work” without the need for adjustments, then you may be better of not using Wayland at this point. Wayland is not ready as a 1:1 compatible Xorg replacement just yet, and maybe never will.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |