4 ms·
But why are management and handling of language-dependent input methods supposed to be in Xorg? What happened to separation of concerns? "Do one thing and do
by dahauns 2y ago
But why are management and handling of language-dependent input methods supposed to be in Xorg?
What happened to separation of concerns?
"Do one thing and do it well"?
- asveikau 2y agoMore like do a thing and do it once. If every WM and DE needs to do it, you have some that don't, or you have issues that are handled correctly by some DEs and not others, etc.
- dahauns 2y agoWe're still talking about Linux, are we? Snark aside, it's still orthogonal to my question. I wasn't questioning whether it should be done centralized, but why it's supposed to be part of the display server protocol/compositor.
- account42 2y agoBecause the "display" server is also responsible for window management and input. Does it have to be this way? Perhaps not - but seperating window management and input is also not trivial. Note that more complex input methods do somewhat bypass the display server and communicate via dbus instead.
- deleted 2y ago[deleted]
- josefx 2y ago> "Do one thing and do it well"? Did you miss the do it well part? Nearly every unix tool does more than one thing, the alternative would be a usability nightmare. * grep, which primarily does pattern matching has dozens of file traversal related flags that could be handled by calling it from find * find, a tool supposed to find files for some reason has dozens of flags related to executing applications which could probably be done by using xargs * did you know that xargs can do pattern matching and replacement on its input string? there are probably dozens of unix tools that are specialized for that