Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wayland in 2021

shibumi.dev

Post reply on HN
Print view View original

91–100 of 146 posts

Re: Wayland in 2021

#91

Post by 411111111111111 »

sz4kerto wrote: post #57
tyfon wrote: post #52

Earlier quoted context omitted.

Do any desktop system handle mixed DPI well? I mainly use Linux so I don't know, but one of my work laptops have windows on it and it freaks out every time I connect it to a 4k monitor. At least in linux I can use triggers and xrandr [1] to manage it even if it's not pretty, never figured out how to do it automatically in windows. Edit: I am using KDE/Qt apps for 99% of my gui stuff. Gnome etc might be worse. [1] htt…

Windows handles it perfectly (anecdotal). Not sure what do you mean by freaking out.

Probably how the scaling is off while you drag windows from/to hidpi displays. The scaling is only adjusted once the pointer moves to the other display.

At least that's how it was for me when I used a high dpi display (160 dpi) 2 yrs ago. (I switched back to 90dpi at some point, so they might have improved it by now)

Re: Wayland in 2021

#92

Post by ElijahLynn »

I am on Arch + Gnome for 3 years now and tried Wayland again this year and experienced too many broken things (Screen.so screensharing, Fireshot screencapture, I think CopyQ clipboard manager too) and had to switch back to X11. This article shows it is still not ready for the masses, yet.

Re: Wayland in 2021

#93

Post by ashkankiani »

halz wrote: post #31

A project to keep an eye on, to replicate 'autotype' support offered by many password managers, is wlrctl¹. A popular alternative is ydotool², but brings some additional risks the operator might not be comfortable with. ¹ https://git.sr.ht/%7Ebrocellous/wlrctl ² https://github.com/ReimuNotMoe/ydotool

re:ydotool. More than risks, I would say the author constantly changing things without testing and breaking the tool is what made me stop using it. I wrote my own version using evdev and never looked back.

Re: Wayland in 2021

#94

Post by sho_hn »

solarkraft wrote: post #72
tyfon wrote: post #52

Earlier quoted context omitted.

Do any desktop system handle mixed DPI well? I mainly use Linux so I don't know, but one of my work laptops have windows on it and it freaks out every time I connect it to a 4k monitor. At least in linux I can use triggers and xrandr [1] to manage it even if it's not pretty, never figured out how to do it automatically in windows. Edit: I am using KDE/Qt apps for 99% of my gui stuff. Gnome etc might be worse. [1] htt…

Works perfectly on Wayfire and I assume Sway. I briefly tried out Gnome and KDE, with the former "meh" (no fractional scaling, scaling glitches when dragging between displays) and the latter garbage (couldn't find scaling settings at all, so nothing is readable on the laptop display). Widows is between "okay" and "nice" (somewhat fractional scaling, glitches between displays, some wrong scalings, but it's rare). I ha…

Fwiw, System Settings -> Display has the per-screen scale settings.

My wife got a 4K desktop screen for her FHD laptop a few months ago and it made us switch her system to Plasma's Wayland session. Mixed DPI works fine, also dynamically (i.e. dock/undock).

Re: Wayland in 2021

#95

Post by sergeykish »

sprash wrote: post #70
scaladev wrote: post #58

Earlier quoted context omitted.

I am a happy Wayland user, and have been for a long time. There are many more out there. You don't often hear us because we don't spend every waking hour shitting on Xorg and praising Wayland for how good it is (maybe we should?) >I wonder if it will ever reach the adoption level of x11 It will, considering that Xorg is effectively no longer maintained and its developers have switched to working on Wayland protocols…

What is the process to become a release manager for X11 without forking it? I assume you can't just walk in there and say "I'll do that".

Who would risk stability? And what is the issue with forking? ffmpeg/libav, openssl/libressl managed fine. No fork is the symptom.

Re: Wayland in 2021

#96

Post by forgotmypw17 »

rnhmjoj wrote: post #84

I think Wayland, and the modern desktop in general too, has forgot about a few good ideas that the original X system had. I will miss them once Wayland has taken over: - A unified way to change applications settings. All old X apps used to read the X resources database (xrdb): you could set a global color scheme, fonts, window geometry and what not, all in one place using a simple but powerful text format. - The simp…

The beauty of free software is that X will always be there for anyone who wants it, just like you can still get great distros without systemd.

Re: Wayland in 2021

#97

Post by erinnh »

ElijahLynn wrote: post #92

I am on Arch + Gnome for 3 years now and tried Wayland again this year and experienced too many broken things (Screen.so screensharing, Fireshot screencapture, I think CopyQ clipboard manager too) and had to switch back to X11. This article shows it is still not ready for the masses, yet.

Flameshot for screencapture and the standard gnome extension clipboard manager work pretty well for me on Wayland.

Cant say anyting about screensharing with Screens.so. Zoom works though.

Ive been a happy Wayland user since 2017 or 2018, not entirely sure.

Re: Wayland in 2021

#98

Post by addicted »

rnhmjoj wrote: post #84

I think Wayland, and the modern desktop in general too, has forgot about a few good ideas that the original X system had. I will miss them once Wayland has taken over: - A unified way to change applications settings. All old X apps used to read the X resources database (xrdb): you could set a global color scheme, fonts, window geometry and what not, all in one place using a simple but powerful text format. - The simp…

> The simplicity of the window managers, hotkey daemons and other X clients. You can implement a functional wm in a few hundred lines of C[1] because the X server takes care of most of the stuff. In comparison a compositor has much more work to do and it's difficult to implement one, unless using a big library like wl_roots.

This sounds like they simply extracted some of the work X used to do into an external library. That sounds like an excellent choice with no particular downside IMO?

Re: Wayland in 2021

#99

Post by erinnh »

ashkankiani wrote: post #93
halz wrote: post #31

A project to keep an eye on, to replicate 'autotype' support offered by many password managers, is wlrctl¹. A popular alternative is ydotool², but brings some additional risks the operator might not be comfortable with. ¹ https://git.sr.ht/%7Ebrocellous/wlrctl ² https://github.com/ReimuNotMoe/ydotool

re:ydotool. More than risks, I would say the author constantly changing things without testing and breaking the tool is what made me stop using it. I wrote my own version using evdev and never looked back.

Could you post a link to it? Ive been using ydotool for a while, its not working 100% reliably though.

Re: Wayland in 2021

#100

Post by erinnh »

ducktective wrote: post #48
chousuke wrote: post #16

Earlier quoted context omitted.

ibus works with Gnome out-of-the-box. On sway/wlroots, you will have more luck with fcitx. I don't know which tool works best with KDE.

Why, in Wayland, support of some basic features has to do with what DE or TWM you use? It is not like this in X11 and it seems there is more adherence to the UNIX philosophy in X11.

Wouldnt it be the other way around? X11 isnt adhering to the UNIX philosophy because it does everything under the sun. Wayland gives some tasks to the compositor.
Post reply on HN