7 ms·
I'd rather not. More people should write wayland clients though, and complain to the makers of existing compositors where they fall short. Which is in a lot of
by yxhuvud 4y ago
I'd rather not. More people should write wayland clients though, and complain to the makers of existing compositors where they fall short. Which is in a lot of places, and they are definitely not sufficiently robust.
- deleted 4y ago[deleted]
- sprash 4y agoThe presenter says that you should not write native Wayland clients at all but use either Gtk or Qt.
- yxhuvud 4y agoThat make no sense. Those are big and doesn't fit all purposes. It would also be a shame as the underlying protocol is just fine and reasonable easy to integrate with, even if it is poorly documented in many places. Which is not really something that can be said about the big toolkits which tend to dictate how execution happen. But that attitude certainly seems common among the people that build compositors. Having more alternative implementations would be very healthy for the environment.
- sprash 4y ago> That make no sense. Those are big and doesn't fit all purposes. It makes sense because Wayland was invented for the purpose of forcing hobbyists and power users into ecosystems that are 100% corporate controlled.