Slashdot Mirror
GTK+ 3.8 Released With Support For Wayland
kthreadd writes "Version 3.8 of the GTK+ GUI framework has been released. A new feature in GTK+ 3.8 is support for Wayland 1.0, the display server that will replace X on free desktops. Among the other new features are improved support for theming, fixes to geometry management and improved accessibility. There is also better support for touch, as part of an ongoing effort in making GTK+ touch-aware."
Being able to make X do something, and doing something without the last 20 years of brain damage are two entirely different things.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
The thing that pisses me and probably others off however is instead the likelyhood of wayland only apps which can't be run remotely like the X ones - then we may as well be on MS Windows.
If you have one fixed software licence for an occasionally used application in an office and it works with X you can just run it on the display of whoever wants it, but if you have the 1980s idea of a dumb local framebuffer you have to reserve a machine for that application and do hotseating. It's stepping back to the single user non-networked idea that was worn out before MSDOS was badly cloned as a cut down single user version of CP/M.
As for X bloat, it runs on Kindles FFS so that should show how stupid the bloat claim is. Would Wayland with gtk perform acceptably on something like a Kindle?
Oh jeez more of the "oh but you can run X on Wayland" crap.
sure, you can eat a shit sandwich too, but it won't be very palatable.
Wayland will enable an X server to run on top of it just like Windows does, just like OS X does
Yeah, and we al know how well that works...
It's terrible. X is very much second class. Here are all the things that don't work:
* Copy/paste of more than text between X and non X
* Remoting of non X windows
* Drag and drop from X to non X
* Pleasant window management of non X windows
whilst enabling a far more efficient and modern rendering pipeline.
Evidence needed, and biased FUD from the Wayland team doesn't cut it.
X has supported direct i.e. nothing in the way rendering for ages now and that is very efficient.
Compositing window managers require a whole extra 2 socket round trips to the kernel *PER MOUSE MOVE*. Given that the kernel has a latency of positively micrseconds this is clearly a big blow for X /sarcasm.
SJW n. One who posts facts.