Put another way: I really hate x86 and Wayland.
The x86 platform is a disaster and a constant source of headaches. I would prefer not to ever touch any x86 machines. Yet I am consistently fixing issues in them for @AdelieLinux so users have choice.
Similarly, I think Wayland is a fool's project and that the effort going in to NIHing a display technology should be invested into solidifying X11 instead. But we still offer Wayland as a second option in Adélie for those who prefer it.
As seen by your example of x86 and wayland, there's often a tradeoff between empowering users and maintenance burden.
I think it's good that you support x86 and wayland in AdelieLinux, even though you don't like it, and have every right to not do it.
Eg. you could say that wayland-related packages should be maintained by someone who likes wayland, or dropped if no such person is found, and that'd be IMO perfectly fine. That'd be sacrificing part of the empowerment of users over your burden, not your feelings.
OTOH, if you said that you will never accept wayland package into your repositories, even if someone else takes care of all the burden it creates, then I'd say it's against the spirit of Free Software. Because that'd be sacrificing part of the empowerment of users to your feelings. That would be spending extra effort to make sure $feature will never be added.
Now let's think of accepting MIME emails. If someone objects to it, then probably it interacts with some software in a bad way.
So accepting such emails is additional burden for some (all?) developers.
But would they still be against MIME if someone volunteered to fix all problems MIME creates? I don't think they would.
@Wolf480pl I already wrote a patch and sent it. It was denied.
Someone else I know sent basically the same patch two weeks before. Denied.
@awilfox Was Wayland not born originally from X developers brainstorming a wishlist of what they'd want to do in a hypothetical X12 if they could break compatibility? X11 is held back by 30 years of backward-compatibility at this point.
X12 hypothetical was written by a completely different group, 3 years after Wayland started. The X12 spec deliberately calls out network transparency and framebuffer support as critical, while Wayland does away with network transparency ("no one cares" per the Wayland dev I spoke to) and virtually no compositors support fbdev.
I'd support what X12 wanted to be; Wayland falls short of that. Maybe with extensions. But then we're right back where we were with X11.
@awilfox @AdelieLinux From the distro maintainer perspective, I can understand not liking Wayland. It's new, it doesn't play nicely with existing applications, it's not necessary, etc. From the perspective of a programmer, I have to disagree with you. Wayland is the answer to a lot of old and fermenting problems. As such, I personally welcome it. No one has to use it, that's the choice of the user. However, to develop is the choice of the developer, not the user. People often forget that.
@awilfox Wayland is to X11 what Ubuntu and derivatives are to Debian
This is a Mastodon instance run by the Interlinked Foundation, a 501(c)(3) non-profit devoted to eliminating discrimination. We are an instance that blocks authoritarian political violence, ultra-nationalism, fascism, the alt-right, Stalinism, and authoritarian ideology in general. It's intended to be a safe place for those tired of violent rhetoric as well as a place safe from discrimination.