> Wayland has a design such that if things don't work for you today we have a hope that we can make it work for you in the future.
The reason we hate Wayland so much is that X is being killed off now, with things only ever maybe working again in the future. Wayland would be way better if the people behind it added support for all of the missing features and use cases first, and only then killed off X.
Right, and I wish them luck. Though signs point to this person not being a good mainainer - breaking basic
features and so on. Maybe this is needed to get into a long term better place though.
Not working with the Xenodm people also seemed like a sign of bad maintainership to me. I don't think the baseline is hard to improve on and him forking it is almost certainly a step in the right direction.
> Though signs point to this person not being a good mainainer
I don't know about that. If you read through the whole issue which was linked, you'll see the guy was quite responsive, fixed the issue very quickly, and gave a reasonable explanation as to the cause of the issue.
> Maybe this is needed to get into a long term better place though.
Yeah, agreed.
I think a separate repo/branch seems like a good place for him to do his work, so he doesn't have to mess with the core repo and has no chance of breaking anything.
I do sympathise with the X maintainers - 1500 commits is a lot to try to keep up with, particularly if you're not very interested in maintaining the thing. I feel like doing the stuff he's doing as a ton of PRs might be a mistake - a separate branch and a couple of huge PRs might have been a better approach.
Maybe he'll be able to make some progress and improvements. That would be cool.
The reason we hate Wayland so much is that X is being killed off now, with things only ever maybe working again in the future. Wayland would be way better if the people behind it added support for all of the missing features and use cases first, and only then killed off X.