4 ms·
If I simply plug and unplug my laptop from the dock, my windows wind up randomly scattered between both laptop and monitor. Is that considered "works"? Lots o
by bsder 3y ago
If I simply plug and unplug my laptop from the dock, my windows wind up randomly scattered between both laptop and monitor. Is that considered "works"?
Lots of people have lots of complaints. I, myself, have more than a few.
I'll go further. The fundamental problem is that Wayland CAN NOT be fixed. The underlying design architecture is simply not correct for modern hardware and its abstractions.
The problem is that a GUI is such an enormous pile of work that nobody can arise to compete with QT and GTK. Both of those toolkits are 20+ years old and desperately need to be redone from the ground up.
And, it's worse than that globally. Mobile/Web GUI and Desktop GUI have fundamentally different abstractions. Yet, because a GUI is such a huge pile of code, nobody wants to have separate GUIs for Desktop and Mobile/Web.
This is why something like Electron exists. No one wants any of the dumbass GUI toolkits--not Windows, not macOS and certainly not Gtk or Qt.
And, yes, I pile Mobile and Web together. Most people now interact with Web via their phone. This is painful to me, but it is simply reality.
- Zambyte 3y ago> If I simply plug and unplug my laptop from the dock, my windows wind up randomly scattered between both laptop and monitor. Is that considered "works"? 1) that doesn't happen on my compositor 2) You can solve that yourself or pay someone to solve it for you. Unless you have a contract, you are not entitled to anyone elses time. > The fundamental problem is that Wayland CAN NOT be fixed. The underlying design architecture is simply not correct for modern hardware and its abstractions. I simply don't care. It works for me, better than anything else I've tried on any operating system. The fact that you disagree with Wayland abstractions has no impact on my real world use. > [...] Both of those toolkits are 20+ years old and desperately need to be redone from the ground up. Great idea, looking forward to your (contractors?) repo :-)
- saati 3y ago> The underlying design architecture is simply not correct for modern hardware and its abstractions Could you elaborate on this?
- vetinari 3y agoHe can't, since the gfx part of Wayland is a thin, event-based abstraction over the modern hardware. It basically manages buffers between the hardware and clients. The comparison to Qt, Gtk or Electron is also very wrong; it is an entirely different layer in the stack.
- yencabulator 3y agoYour first clue to it being a worthless rant was confusing window layout decisions with the Wayland protocol.