Live data from Hacker News

Wayland is not ready as a 1:1 compatible Xorg replacement just yet

gist.github.com

371–380 of 419 posts

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#371

Earlier quoted context omitted.

There are a ton of long standing security issues. Which is why they are working on wayland: X11 isn't possible to secure as bad security is part of how it works.

My desktop is not a smartphone where I download random shady apps from an app store. I don't need any of the "security" wayland offers. If I don't trust some software I simply won't apt install it.

You are not the only user.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#372
post #355

Earlier quoted context omitted.

My 3840x2160 external monitor has a pixel density of approx. 275 ppi. IIRC it cost approx. $300, not exactly prohibitive.

This sounds like an interesting screen. Which is it, if I may ask?

That sounds like a rather standard 27" 4K display of which there are several on the market.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#373

Earlier quoted context omitted.

You don't even need a compositor. Just activate Force Full Composition Pipeline if you have an nvidia card. see: https://imgur.com/a/lDfObqw It's in the advanced settings. Silky smooth Xorg web browsing and video at no extra compositor cost.

Thank you so much for this! I've been looking for a solution in picom config for way, way too long.

You're welcome.

Frankly I have no idea why it's not enabled by default.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#374
post #368

Earlier quoted context omitted.

Something that isn't particularly good 12 years in will likely never be so. At 12 years in some really basic stuff is just now rolling in. In general the idea of natural progress is completely imaginary. The general nature of things is to get worse not better entropy always wins.

X isn't particularly good either, and even older ...

It night not be great but it does many things Effectively and doesn't require each graphical environment to individually handle low level hardware details.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#375

Earlier quoted context omitted.

Show stopper for Ubuntu was screen capture. So screen capture works today, and if they switched, if would be difficult only for the first few weeks, when Ubuntu is buggy anyway. But they didn't and the long-term consequences of delaying it will be felt across all linux distributions for years to come. So much for appeasing RH and it's fanbase.

I disagree, this happened before with pulseaudio, it was not ready and for years people would recommend to remove it, so the leason is not replace something that works now with something that is shiny but might work next year. I also think NVIDIA had a role in this default display issue, Ubuntu has to use something that actually works on all hardware combinations,competent users can install and try a Wayland implemen…

There are still people who uninstall pulseaudio, because "bloat" and then harass authors of audio applications to support their snowflake system.

The forced PA brought some pain. but it forced swift improvement in audio drivers. Without it, we would still have half-buggy drivers that do not really work.

Regarding Nvidia: all distributions that switched to Wayland default switched that only for supported hardware, so Nvidia users are still getting X11. I don't expect Ubuntu doing it differently.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#376
post #368

Earlier quoted context omitted.

X isn't particularly good either, and even older ...

It night not be great but it does many things Effectively and doesn't require each graphical environment to individually handle low level hardware details.

Yes, and it is about to die.

Wayland could have been executed better to ease adoption, no doubt. More than anything momentum is required, which we arguable are beginning to see.

The question today isn't X vs. Wayland. It is Wayland vs. Y. Whatever Y is.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#377
post #229
post #208

Earlier quoted context omitted.

All major distros seem to have agreed on Flatpak/Freedesktop Portal dbus APIs. For eg, for screenshot : https://docs.flatpak.org/en/latest/portal-api-reference.html... There are still apps using legacy gnome/kde specific APIs, but, from what I understand, in the future Flatpak APIs are becoming the defacto standard

These are dbus APIs though, not wayland protocol specifications that you can call with libwayland's RPC mechanism. On the one hand this means you can support both X11 and Wayland with a single API from a client perspective, on the other you have to use DBus, which is horrendous to use (especially from statically typed languages). It also doesn't seem to work on my XFCE/X11 desktop, which shows what fragmentation we h…

Not all statically typed languages. Using it in QT is great, and using it in GTK in C is not more difficult than showing a window. I also recently came across zbus in rust (https://docs.rs/zbus/1.8.0/zbus/) and it looks like it’s similar dynamically typed languages. I’ve also heard good things about the Systemd implementation. In all of these situations, it’s far easier to use DBus than another Wayland protocol.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#378
post #283

Earlier quoted context omitted.

What makes you think uinput is less capable? Ultimately everything that uses input uses uinput, it's the source of truth.

For the same reason that it can make sense to say that python is more powerful than C, even though you can obviously do more things with C than with python. Xdotool lets you send keystrokes to a particular window, even if it's not in focus. You can do that with ydotool if you also do some sway IPC, but it's not as convenient, and no one has made a higher-level tool, possibly because it would be a nightmare to make it…

Actually, xdotool is the wrong place for this kind of automation. IMO, the optimal place to implement this is in the toolkits, to make it possible to read text and properly click buttons and menus.

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#379
post #145

Earlier quoted context omitted.

That's a shame, I enjoy playing with ML so having no CUDA available is a bit of a showstopper there. For graphics I'd like to switch to AMD, but right now you just can't buy their higher end consumer cards.

To be fair you can't buy any 3000 series Nvidia card either.

Quite true! Let's be balanced about it.

In this case I already have a 2080Ti, which gives my previous comment context. If I was starting from scratch then, well, I'd be stuffed either way :)

Re: Wayland is not ready as a 1:1 compatible Xorg replacement just yet

#380

Earlier quoted context omitted.

> This post is a bit too ranty for its own good, but it has a valid point, and one that is unfortunately common in the open source community: because you have no monetary obligation to your "customers" (=users), there's not really a lot that forces you to maintain backwards compatibility. And yet, distros like Ubuntu are too conservative, because they are too careful not to break something. Their signalling is then c…

I don't know if everyone is fine with Apple making so many changes. I think it's because they have no choice, being stuck with whatever Apple decides. eg. for years you couldn't resize a window from the left edge and everybody was "fine" with it. When they actually bothered to implement it, it was astounding to think you couldn't do it before! As for me, I await each Apple release with trepidation and fear. Will my a…

I abandoned Mac OSX for Win 10 (manager half of brain) and Linux (dev half of brain) years ago.

It got really tiresome rebuilding my dev environments in particular with every new release. Butterfly keyboard, touch bar, and other hardware choices were additional hindrances. Infuriating design choices like doing away with 'Save As' were the last straw. I don't really care about UI improvements, to be honest. OSX Leopard was usable for everything I do in normal life.

Post reply on HN