3 ms·
s/That particular X developer/All X developers, except maybe for Keith Packard/g The X development community has decided, almost unanimously, that Wayland is t
by bitwize 6y ago
s/That particular X developer/All X developers, except maybe for Keith Packard/g
The X development community has decided, almost unanimously, that Wayland is the way forward. More powerful and knowledgeable forces than you have cast this die for you. It is now upon you to either adjust, or step up and contribute where Wayland is lacking.
- mixedCase 6y agoOr, we could just use X if it still works for us. I don't need any "more powerful and knowledgeable forces" to tell me what works for me and what doesn't. I'd like to use Wayland. But there's no replacement to my bspwm+picom setup that works with a little configuration. Tough luck, guess I won't be using Wayland for now.
- bitwize 6y agoYeah, except what happens when the apps and toolkits you use drop X support because they consider X a dead end? What will you do then? This is NOT a hypothetical. Projects have dropped ALSA support and adopted a policy of PulseAudio or GTFO -- and ALSA has more commitment to its long-term maintenance than Xorg now does. And I suspect the next phase will be Wayland maintainers putting pressure on toolkits to drop X support, much like Lennart pressured the GNOME community to hard-depend on systemd.
- djur 6y agoAt that point the Wayland ecosystem is hopefully mature enough to make the switch less painful than it is now. I don't see anyone saying they'd rather toss their computer in the garbage than ever use Wayland, just that it doesn't currently meet their needs.
- sergeykish 6y agoI do not think it is wise to spread fear. Fear is the reason people attack Wayland. Lets keep them separate. I have no PulseAudio, solved Skype with apulse, though I don't use much media except browser, player and tuner.
- account42 6y agoSame as with ALSA - I either stop using those apps, patch ALSA/X11 support back in or use wrappers to do the translation for me.
- michaelmrose 6y agoThis is an interesting dichotomy. Alternatively just keep using X until 2030. If X does everything you presently care for well and major apps like gimp and firefox are apt to support X for the next decade an alternative contribution might be bug fixes for X or packaging for distros that opt to continue to support it. When about do you think firefox will no longer build for X? Python 3 was ready in 2008 but 2 will be supported by RHEL until at least 2024 16 years later. I will be surprised if in 2030 I can't simply pick distro with X and fire up firefox.
- michaelmrose 6y agoThis is an interesting dichotomy. Alternatively just keep using X until 2030-2040. If X does everything you presently care for well and major apps like gimp and firefox are apt to support X for the next decade+ an alternative contribution might be bug fixes for X or packaging for distros that opt to continue to support it. When about do you think firefox will no longer build for X? Python 3 was ready in 2008 but 2 will be supported by RHEL until at least 2024 16 years later. I will be surprised if in 2030 I can't simply pick distro with X and fire up firefox. Its kind of silly to expect users who are disinterested in using foo to pitch in to make foo acceptable when said users really want bar because you tell them that bar is now the standard "get over it".
- bitwize 6y ago> When about do you think firefox will no longer build for X? Firefox? 2025 at the latest. Firefox was the project that deprecated ALSA a few years back. Now that all major distros ship with Wayland as the default, it's time to assume Wayland and not assume X. Eventually X support will become burdensome, and be removed.
- michaelmrose 6y agoYou can still build Firefox with Alsa support and probably still will be able to in 2025. The majority of users are still using x11 which is why for example Firefox just added hardware decoding under X last month. Optimistically for wayland this might change between 2024-26 at which point application developers can stop supporting it at which point people who are so inclined can provide an x11 build of Firefox in 2026-2028 which are liable to work through 2030. In a less optimal world we are still in step one in 2030. Anyone who thinks X is going anywhere this decade is dreaming.
- bluGill 6y agoThe other option is to maintain X. I'm not interested in that, and since thise who have done that in the past agree Wayland is the future I'm cautiously going to trust them and so I'll transition my systems to Wayland (if they are still x).