I don’t know if you’ve tried it yet, but setting the “Haptic Touch” option to “Fast” gets you a bit closer to what you could do with 3D touch.
It’s under Accessibility -> Touch -> Haptic Touch
Personally I like it better vs the default setting.
I’m just here mainly to keep up with the news around Linux.
I don’t know if you’ve tried it yet, but setting the “Haptic Touch” option to “Fast” gets you a bit closer to what you could do with 3D touch.
It’s under Accessibility -> Touch -> Haptic Touch
Personally I like it better vs the default setting.
I think in terms of hardware it’s worth it if you value the convenience. Stuff like the Apple Watch, Airpods, iPad, Apple TV, is good hardware and they work well together.
On the software side you can use cross platform software wherever possible to not rely as much on Apple’s services, in case you wanted to switch, then it would be too difficult
I copy everything in my home folder and paste it all in the new installation. Works well if I stick with the same desktop environment.
I think it’s worth noting that Tumbleweed also has the Mesa/codecs situation, where if you want the codecs you have to enable the Packman repo and install mesa from there, and when there’s an update for mesa you have to wait for the update on Packman repo, otherwise you get some conflicts when trying to update. Though packman usually updates quick enough so it’s usually not an issue but it can be a bit weird the first time you see it.
Aside from that yeah, Tumbleweed is great. Though i’m currently running Fedora Kinoite and overall I’ve been happy with it, but I would probably go back to Tumbleweed if something were to happen.
Here’s some info on it: https://userbase.kde.org/KWin_Rules
From the overview:
KWin allows the end-user to define rules to alter an application’s window attributes.
For example, when an application is started, it can be forced to always run on Virtual Desktop 2. Or a defect in an application can be worked-around to force the window above others.
I faced this as well on KDE and got around it by creating a window rule to match it by window title and force a .desktop name to the vs code window, so it shows the correct icon on the taskbar. I wonder if there is a similar functionality on Gnome?
I’m pretty sure it’s wayland because on KDE wayland, with 200% scaling, when the cursor is over an xwayland window, it looks blurry. This doesn’t happen on wayland windows. Also for some reason electron and chromium based apps run at 60 fps on wayland, while xwayland apps run at 144 fps as it should, and my VS Code in the Distrobox with the wayland flags also runs at 60 fps. Weird KDE stuff.
Yes. I run VS Code in an Ubuntu distrobox, with the electron wayland flags. Works real nice. KDE Wayland btw.
On KDE there’s System Monitor, which you can customize to show graphs for CPU usage and temp, among other things, and GPU usage and temp too.
For in-game monitoring there’s Mangohud, also very customizable on what you can show in the overlay