← Back to context

Comment by lelanthran

13 hours ago

> It's come across to me so far that this just results from application developers targeting a specific DE and not really thinking about compatibility, or even really whether they need specific functionality provided a specific way.

They are, but it's not their fault - Wayland removes so much functionality that X had, and delegates that to the WM/DE.

I tried to do a small personal app last year for myself that intercepted and injected events for keyboard and mouse. Not possible in Wayland (so I switched to X instead) - that is delegated to the WM/DE.

There's hundreds of these tiny little cuts that cause friction for app devs.