6 ms·
Interesting for a dist focused on resource constraints to be using the new/shiny instead of old and small. Perhaps W is more efficient? > Q: Why are you switc
by mixmastamyk 8y ago
Interesting for a dist focused on resource constraints to be using the new/shiny instead of old and small.
Perhaps W is more efficient?
> Q: Why are you switching to Wayland?
A: The X implementation is old and won’t be updated to address the way desktop Linux is used today. Window managers are an afterthought, and many things aren’t implemented correctly. Wayland is a modern take on the Linux display system.
Would have liked if this was expanded on a bit. Using X on 18.04 now and while not perfect (in the security area) nothing else about it is currently holding me back.
- dunpeal 8y agoIs it a fact that X is "smaller" than Wayland, and more resource efficient? X was designed with far more ambitious goals than Wayland, so it's not a foregone conclusion that it's "smaller" (implying cheaper) just because it's older.
- emersion 8y ago>Is it a fact that X is "smaller" than Wayland, and more resource efficient? This statement doesn't really make sense. Wayland is just a protocol, and you can build bloated compositors on top of it -- just like you can build really tiny compositors [1]. xorg-xserver on the other hand will always have the same level of "bloat". >X was designed with far more ambitious goals than Wayland This is hard to say. Wayland has been designed to be flexible enough to allow for a clean base that can be used in mobile UIs, IVIs (e.g. plane UIs), VR and so on (without hacks). [1]: https://gist.github.com/SirCmpwn/ae4d1cdcca97ffeb2c35f0878d75dc17 https://gist.github.com/SirCmpwn/ae4d1cdcca97ffeb2c35f0878d7...
- dunpeal 8y ago> Wayland is just a protocol If we're splitting hairs here: X (i.e. the X11 Window System) is also "just a protocol".
- emersion 8y agoSure, but then it's quite difficult to say that one is "more resource efficient" than the other. Only implementations can be compared. And in fact, when you e.g. open Gedit, hundreds of messages are exchanged on X11 (getting/registering atoms, changing window properties, etc). Wayland is much more efficient in that regard.
- dunpeal 8y ago> Wayland is much more efficient in that regard. Which is what I implied in my original comment... Of course, the resources are ultimately consumed by implementations, not protocols. But it helps when the protocols are efficient.
- mixmastamyk 8y agoIn the sense that I first used X on Linux on a 486 in the early/mid 90's. It was snappy then and snappy now. Also I like being able to minimize crashed windows, something other major OSs haven't done.
- dcbadacd 8y agoBut screen tearing is a plague on so much different hardware and multi-monitor, high-dpi, FreeSync, HDR, high-gamut (pick any combination of these things) really do not want to work perfectly with X. This is not to say Wayland is good, X Forwarding is an awesome feature and X runs probably can now run on a literally toaster.
- mixmastamyk 8y agoI'm using it with two 4k monitors now, no problem, and no screen tearing. Hi-color might be somewhat compelling, though I write text files for a living. Does X not support it?
- dcbadacd 8y ago> Does X not support it? It technically should, but there's no official page that says it does (and in which combinations) and then there's the question if the DE and other software Linux does. It all in total has a probability of breaking, combine a few rare features and it's pretty much certain something will break. It would be really awesome if say phoronix tested all of those features out in every combination :D
- acdha 8y ago> Also I like being able to minimize crashed windows, something other major OSs haven't done. What major OSes besides Windows and Mac OS did you have in mind?
- mixmastamyk 8y agoThose are the two I'm thinking of. May have changed however, haven't used either extensively in several years.
- kenmicklas 8y agoX is much larger than Wayland in the same way that OpenGL is much larger than Vulkan. The older protocols tried to encode way too much framework-like application implementation details which turned out to be a mistake. And in both cases, the framework layers (GUI toolkits, game engines) ended up reimplementing most of that logic but better, leading to lots of unused cruft and problematic architecture in the lower layer.
- bitwize 8y ago> The older protocols tried to encode way too much framework-like application implementation details which turned out to be a mistake. What "framework-like application implementation details"? I came to X development from Windows development, and the first thing I noticed was the lack of stuff bare X provides. X doesn't even have timers, let alone a standard notion of how to display a button or text box. It's very bare bones and minimal, and you can learn most of it in a weekend. (I know, because I did.) Game engines need OpenGL to work, so no surprise they reimplemented much of the rendering layer. GTK is maintained by fucking GNOME developers who run screaming at the sight of old code they have to maintain, so reimplementing fucking everything is par for the course for that crowd. If Wayland ever settles down and becomes usable, within a few years the GNOME team will be lamenting how old and crufty it all is and making plans to replace it with an even newer graphics stack. EDIT: X actually does have something like timers, in the XSync extension.
- mixmastamyk 8y agoBelieve grandparent is talking about Xlib, etc. True not used much any more, but they don't hurt anything sitting on disk. And as mentioned elsewhere targeted at 80's and 90's hardware.
- bitwize 8y ago> Believe grandparent is talking about Xlib, etc. They mentioned "the old protocols". Xlib is not a protocol. And it's not a framework either. > And as mentioned elsewhere targeted at 80's and 90's hardware. Yeah? And? The DEs that are targeted at 2010s hardware have compositing-latency issues, slow animations, and seem to have trouble making it clear what can be clicked on. I know because any time an article about the Windows 9x UI comes up, Hackernews goes on a nostalgia-tinged, but justified, rant about how great that UI was and how easy it was to read what can be interacted with and how. Maybe the 80s and 90s got a lot right in terms of UI, and constant UI churn just isn't necessary. Besides which, if you can build a UI that could be run on a 90s PC, it takes up far fewer resources than do the UIs of today, and that's compute that you could devote to better programs. And Xorg accelerates the old X and newer Xrender primitives with the GPU anyway, through GLAMOR, so it's not like you're not taking advantage of it.
- jplayer01 8y agoFirst time I've seen 'small' being used to describe X.
- bitwize 8y agoX was running on 286-class machines (that were intended as purpose-built X terminals) back in the day. The KDrive server can be compiled to fit in a few hundred KiB.
- babypuncher 8y agoX today is a different beast than it was 20 years ago
- bitwize 8y agoAnd the KDrive server can still be compiled to fit in a few hundred KiB. And it's a full-featured X server. X is small, especially when you start comparing it to the sort of runtime modern devs are fond of (looking at you, Electron).
- emersion 8y agoNothing stops you from building a very small Wayland compositor.
- cs315 8y ago>Interesting for a dist focused on resource constraints to be using the new/shiny instead of old and small. Lubuntu has shifted focus recently https://lubuntu.me/taking-a-new-direction/ https://lubuntu.me/taking-a-new-direction/
- mixmastamyk 8y agoAhh, I see. Computers have been good enough for a decade or more and therefore not much reason to support ancient machines. A ten-year old computer is probably close to free.
- starsinspace 8y agoWell, I'm using X on Xubuntu 18.04, and I'm still constantly annoyed about seeing tearing artefacts when playing video. This is something that should have been solved >15 years ago, but somehow, it still isn't.
- mixmastamyk 8y agoI do have an occasional stutter with HD+ video running fullscreen with VLC, but otherwise hadn't noticed. Hopefully W improves on that.
- cultus 8y agoDon't assume that new=complex. Wayland is smaller and follows the Unix philosophy much better than X. X has gotten insanely complex with all the workarounds necessary for a modern desktop. It tries to do far too much, and not well, so all the other parts replicate much of X's functionality. Wayland was actually started by X devs who felt it needed a reboot.
- captainmuon 8y agoWayland and X11 are complex in different ways. Wayland is a simpler spec without years of cruft, but it is much more complex to write a Wayland compositor than a X11 Window Manager. There are libraries like wlroots, but they are opinionated. And it will still take years for Wayland to match X11 feature wise (screenshots, eyedropper tools, a remoting option, restarting the window manager or compositor independently of the desktop, and so on). I fear that the switch to Wayland will slow down experimentation in the field of window management, because it makes it hard to quickly do something different. Which would be ironic given the goals of it.