Re:More developers use Linux than Mac, according to 2022 Sta...
by jchw on Wednesday December 28, 2022 @02:12PM
(#34164599)
If you are on Wayland, fractional scaling should be working fine as of 2022. It'll be a little blurry in some cases until everything is native Wayland and fractional scaling is supported through all apps and compositors, but at the very least window geometries should be being scaled correctly unilaterally when you run Wayland today, heterogenous DPI, fractional DPI, whatever.
Can't comment on scroll inertia. Libinput has been working pretty well with my assortment of trackpads. Touch input seems ok on Wayland too, using an ITHC based device.
Have not had the sleep problem with Linux lately. Actually, the problem has kind of reversed - nowadays, this problem is more associated with Windows, thanks to Windows Modern Standby being impossible to disable on newer Intel processors. Still, sleep may be broken if you are using an NVIDIA based device. All I can say is, NVIDIA is one thing better avoided with Linux today. Obviously, if you want your best shot, using hardware that is designed and tested only on other OSes that has merely reverse engineered support in Linux is not going to give it to you, though I understand why people are not willing to fork the cash over to one of the few vendors like System76 that actually do a reasonable job.
You got me on clipboard management, that sucks today. I'm pretty sure it's not impossible in Wayland, but it'll need compositor support. KDE on X11 used to have great clipboard management; dunno what the status of that is in 2022, as I used KDE most in the KDE3 days. Clipboard management is hard for valid reasons though. Just like on all other operating systems, clipboard isn't really a place that data lives, it's an IPC layer. When you copy, nothing happens except for the advertisement that something has been copied to the clipboard. Sometimes clipboard operations hang if an app becomes unresponsive, and the act of "pasting" is not necessarily without side-effects. This makes active clipboard management pretty hard to get right, if it's possible at all with today's designs. The biggest problem is LOSING the clipboard when an app closes, in some environments. That really does need to be fixed. That said, believe it or not, it happens on Windows too, just, thankfully, not in most common scenarios.
Can't comment on scroll inertia. Libinput has been working pretty well with my assortment of trackpads. Touch input seems ok on Wayland too, using an ITHC based device.
Have not had the sleep problem with Linux lately. Actually, the problem has kind of reversed - nowadays, this problem is more associated with Windows, thanks to Windows Modern Standby being impossible to disable on newer Intel processors. Still, sleep may be broken if you are using an NVIDIA based device. All I can say is, NVIDIA is one thing better avoided with Linux today. Obviously, if you want your best shot, using hardware that is designed and tested only on other OSes that has merely reverse engineered support in Linux is not going to give it to you, though I understand why people are not willing to fork the cash over to one of the few vendors like System76 that actually do a reasonable job.
You got me on clipboard management, that sucks today. I'm pretty sure it's not impossible in Wayland, but it'll need compositor support. KDE on X11 used to have great clipboard management; dunno what the status of that is in 2022, as I used KDE most in the KDE3 days. Clipboard management is hard for valid reasons though. Just like on all other operating systems, clipboard isn't really a place that data lives, it's an IPC layer. When you copy, nothing happens except for the advertisement that something has been copied to the clipboard. Sometimes clipboard operations hang if an app becomes unresponsive, and the act of "pasting" is not necessarily without side-effects. This makes active clipboard management pretty hard to get right, if it's possible at all with today's designs. The biggest problem is LOSING the clipboard when an app closes, in some environments. That really does need to be fixed. That said, believe it or not, it happens on Windows too, just, thankfully, not in most common scenarios.