By all means feel free, but know that you commit yourself to an endless task; every compositor has to have every feature implemented independently. The big two, GNOME and KDE, will need to be handled completely independently. After that, you can ease the process by getting support into wlroots, but that merely makes it easier per compositor; you'll still need to submit patches to every consumer of the library to actually wire up support. (For a worked example: wlroots has a way to set the keyboard layout. This does not mean that every compositor using wlroots has a way to set keyboard layout.)

▲

nitwit005 18 hours ago | parent [-]

You're essentially encouraging people to give up and leave it broken.

Sure, a lot of code changes need to happen, but they only need to happen once. There's no real reason to discourage people from stepping closer to the end goal.

	▲	yjftsjthsd-h 17 hours ago \| parent [-]
		Like... I don't exactly want to discourage people. As a person using a11y tools that don't yet exist on Wayland, I would kinda like to be able to migrate over. But it remains true that Wayland is set up in such a way that it's inherently a longer uphill struggle, and always will be. If tomorrow someone created a new X11 window manager, I could switch and my tools would still work. If tomorrow someone created a new Wayland compositor, I almost certainly couldn't use it, because they'd need to implement everything over again. They can do that, obviously, but the startup effort will always be higher.