Hacker News Reader

Comment by bionade24 | Hacker News Reader

Because X11 is such a joke. The problem is solved by wlroots and layer-shell, other Wayland compositors probably have similar things. Swaylock works 100%ly reliable until now (For me). I had problems with every other X11 screenlocker I used in the past. My unusual setup with a docking station and two monitors on it often caused crazy bugs.

Edit: For me stuff

View on HN

It seems like most of the complaints I see about distros have actually been solved problems for years but held back by poor distro defaults.

I have been recommending fedora to people for a while because their defaults are far more modern and sane rather than clinging on to python 2 and X11

But then you are breaking enterprise stuff !!!1!11!

My favourite moment was when fedora turned on CGroups v2 after every distro waited years for docker to update to it. Docker was broken on fedora until you manually turned v1 back on but then docker suddenly upgraded to support v2.

Other commenters link to similar issues with Wayland screen lockers. So I am not sure how the current shiny fixes things.

> python 2

In contrast to Wayland that can be installed in parallel to python 3. So the only reason to remove it is if you enjoy breaking working software.

Its not that they still had python 2, its that the binary "python" referred to python 2 on ubuntu (it might even still be like this) while other distros had it pointed to python 3.

Given that python versions are incompatible by design you should probably explicitly refer to the version your code supports. At least that is my takeaway from this mess.

This whole situation is a bad trap for novices, given how many tutorials, class slides, etc ask students to copy/paste various invocations of pip and python that may or may not work verbatim on their distro.

Breaking stuff is the first step towards learning to fix stuff.

It's complicated: https://lwn.net/Articles/780737/

The difference is that with Wayland there are no design issues that prevent you from implementing it reliably and securely; if it's broken it's an implementation problem that can be fixed.

Also:

> In contrast to Wayland

I don't think Wayland is what you think it is.

What's your take on the issues listed by formerly_proven[0]?

0: https://news.ycombinator.com/item?id=25844338

I'll edit it to (for me). With working on an X11 desktop everyday, it felt like everyone has at least once experienced such an issue.

To be fair to swaylock, they actually fixed some of those issues, in contrast to kscreenlocker which are just ignoring most edge-case bugs, because it's nearly impossible to fix them.

It's still a fundamentally flawed design, because the system fails open when the locker crashes. So it seems Sway / Wayland actually didn't learn anything in this area, and suffers from exactly the same problem as X11 when it comes to the lockscreen.

Reply on news.ycombinator.com