3 ms·
> The concept of Wayland is great and well-implemented. The implementation of Wayland is bad. I'm going to disagree; some Wayland implementations of Wayland ar
by yjftsjthsd-h 4y ago
> The concept of Wayland is great and well-implemented. The implementation of Wayland is bad.
I'm going to disagree; some Wayland implementations of Wayland are good, but the concept is bad. Wayland is a beautiful, elegant protocol that does almost nothing, instead delegating everything more interesting than "display these pixels" to other protocols. That could have worked, but in reality nothing else was actually standardized (n.b. if a "standard" isn't implemented by GNOME, KDE, and libroots, it's not actually a standard), so there is no useful "Wayland" only many Wayland implementations. If you pick an implementation that covers every feature you want, it's great! And if you ever want anything it didn't implement, or ever want to use software targeting a different implementation, you're stuck. Thus, I say Wayland is a bad concept, because it ensures that everyone will be forever reimplementing everything, incompatibly.
- kaba0 4y ago> Thus, I say Wayland is a bad concept, because it ensures that everyone will be forever reimplementing everything, incompatibly. Why do you think that? There are some arguments on bleeding edge protocol proposals, but once they are wide-spread enough they seem to get implemented by everyone equally well - causing apps to depend on them and solidifying those. I don’t see any problem here, the slight slowness of certain proposals is simply the bazaar style development where unlike Apple, linux can’t just decide on a fix thing, it has to get a certain network effect going for it firts.
- yjftsjthsd-h 4y ago> Why do you think that? There are some arguments on bleeding edge protocol proposals, but once they are wide-spread enough they seem to get implemented by everyone equally well - causing apps to depend on them and solidifying those. Bleeding edge? As far as I can tell, GNOME and wlroots still have incompatible APIs for screenshots. > it has to get a certain network effect going for it When it takes years to get network effects for little things like screenshots and screen sharing, I certainly see a problem here.
- vetinari 4y agoIt is lesson from X11. X11 has many things, for example drawing primitives in core; nobody uses it, but it has to be there, because it was specified so. Wayland extensions, not being mandatory, solve exactly this problem - if something is not used, it could be removed and clients will know very well, that it is not there.
- yjftsjthsd-h 4y agoI can easily agree that X11 had a problem with way too many things in the core spec, and I'm 100% on board with breaking things out. The problem is that they shipped the thing with none of the additional extensions actually defined, which meant that when people went to implement everything outside of the (correctly) tiny core they implemented things differently and incompatibly. It's like a return to the days when the web had multiple major browser engines, and every time you wanted to do something you had to look up what browsers implemented it and what charming little quirks each implementation had.
- vetinari 4y agoIt was actually a case with X11 too... it took some time to converge on XFree86, or what became X.org eventually. Yes, it is annoying, I agree, but it will get better.
- yjftsjthsd-h 4y agoI'm not sure it can get better to the same degree. With X, we ended up mostly with X.org dominating the space, and that meant that it became the de-facto standard way to do certain things - I honestly don't know how many of setxkbmap, xrandr, clipboard management, color management, etc. are X11 features vs X.org features, but either way they were all centralized and worked the same no matter what window manager or desktop environment you put on top of Xorg. With Wayland, there's nothing to ensure that they will converge; GNOME can pick a way to do keyboard layout and just stick with that forever, and wlroots can pick a way to do keyboard layout and just stick with that forever, and users will forever be stuck having to look up how each compositor does or doesn't support changing keyboard layout. (This is not an idle problem to me; I recently found a wayland compositor that I wanted to try, and discovered that in spite of using wlroots it didn't actually expose any way to configure keyboard layout. With a X11 window manager, I'd just run setxkbmap and be done, but with wayland it's literally impossible for me to solve without writing code.)