I wouldn’t be so sure they will double down on it forever. I remember too many stupid MS actions like early 2010’s convergence and metro UI because touchscreens and shit, where is it now?

I wish Microsoft keeps up with its AI obsession and push as much as possible. At some point they’ll realize the reputation damage, but the longer it will take the better. Just stop the negative publicity

I wish Microsoft keeps up with its AI obsession and push as much as possible. At some point they’ll realize the reputation damage, but the longer it will take the better. Just stop the negative publicity

It’s bad Windows gets so much bad press these days, the longer they stay in denial the better

Unlikely, cons0omers don’t buy ideology and don’t care about reason. They want to pay money and get complete product that is easy enough for person with not too many brain connections, not to just justify missing features for values.

Well, if you honestly think about it, Linux has always been tried by many of people that eventually went back to Windows because something wasn’t entirely straightforward. Don’t get me wrong, I love Linux, but I don’t blame people for thinking that. Trying Linux is very different than sticking to it. Linux is amazing OS for people who put at least some effort into learning it, but like it or not, it can be absolute pain for those expecting things to just work without any interest on why they experiencing issues. Given how many sets of hardware and peripherals people have, weird quirks, bugs and required workarounds aren’t unheard of. Maybe it’s just something very simple to fix for an advanced user, but normies will just run away.

They said there’s still a lot of work for them to do with SteamOS before it’s usable on all PCs. I wouldn’t hold my breath especially if you’re on NVIDIA, especially if it’s older than RTX-es. Besides, when SteamOS is ready for general public, the desktop Linux experience is elsewhere regardless of the distribution.

You could’ve just ask ;)

To fix Xbox controller connect it to an Xbox console and update its firmware.

To fix some videos not playing in games, switch from stock Proton to GE-Proton, you can install ProtonPlus or ProtonUpQt from your desktop store for easy Proton installs, newly installed Proton versions show up after Steam restart.

Skurvysyně bobře

Webcam is just USB device, you can passthru that to the VM and it will work. Microphone is part of your onboard audio device, but it can probably be configured somehow to also expose microphone on an emulated audio device inside vm, but idk

Find jellyfin related file in /etc/apt/sources.list.d, edit it as root and try replacing „circle” with „bookworm”. After that apt update and retry. If it doesn’t work you can also try replacing it with „noble” but the you might also need to replace debian -> ubuntu, but that’s just my guess

What you really need is one of native DAWs you mentioned combined with Windows VST plugins run using Yabridge + WINE.

I remember running even complex VSTs along with realtime MIDI processing from e-drums with really good results and low latency.

1. Make sure your distro runs Pipewire and has pipewire-jack installed. Run your DAWs with JACK backend

2. You can check https://wiki.archlinux.org/title/Professional_audio for tips regarding audio performance. Don’t worry if you don’t use Arch-based distro. Most of it applies to any distro really

3. Install wine and yabridge follow setup instructions on how sync your plugins, which essentially takes specified locations with VST2/VST3 DLLs and creates .so equivalents (Linux dll format) under specified location that under the hood calls Wine, but makes it transparent. You add that location (with .so files) in your DAWs search paths and it should scan those plugins like if they were native.

Of course some compatibility issues are possible, but you should be able to run most stuff this way when it comes to plugins.

I’m pretty sure I used SyncThing from Flatpak at one point and it run great

Thank you very much Tim Apple

You don’t need to. Modem browsers will suspend unused tabs, cache them on drive and free up the memory, while quickly restoring as soon user activate them. On at least moderately fast systems this happens so quickly it’s hardly noticeable.

I’m pretty sure it is or at least will be at some point

Thanks for nothing Microsoft

That depends on which GPU you’re using as nvidia-open is for Turing and newer, but that makes no practical difference as it is and will always be out-of-tree.

It really depends on how the distro you’re using is integrating them and while installing them is usually the easy part, working around certain quirks they come with can be a bit tedious in my experience.

The proprietary driver comes in binary form and is shipped with a small kernel module that handles loading the binary driver. The Linux kernel modules that aren’t part of Linux itself (which most drivers are) must be compiled for specific kernel and its binary can work only for that specific kernel and nothing else. This means that even if then driver is the same but kernel changes, the nvidia module must still be recompiled. There are two ways distros handle that: 1) by running the compilation process in the background while installing or updating the driver package 2) by shipping binary form of the nvidia module, in case where it’s distro that always recommends synchronization of all packages so that kernel and modules always match. Historically this caused way more problems than it sounds, compilation might have failed for certain kernels occasionally leaving users with broken video after simple system update. Overall though it mostly works fine, especially nowadays.

Another quirk is that the user-space part of the driver that exposes OpenGL and Vulkan interfaces for applications are also proprietary and closed source, and they must also match exactly with the kernel part of the driver. This creates another problem for sandboxed applications using for instance Flatpak. Applications in container won’t use the system-wide libraries, but rather ship their own - and that’s by design for good reasons. Flatpak will automatically detect NVIDIA and install matching driver just fine, but then after installing system upades, you must always update your flatpaks as well or the ones that use GPU in any way will simply fail to launch or fall back to software rendering making it extremely slow. This doesn’t happen for open source drivers, because Mesa can work with basically any kernel, so Mesa in Flatpak can be in completely different version than the one installed as system package. Moreover, I experienced problems with storage space because Flatpak wouldn’t automatically remove old NVIDIA drivers and after a year or so it was a chunky pile of NVIDIA drivers.

And even when it works, there can still be missing functionality or integration with the OS might not be perfect. Last time I used them I was limited to X11 with many quirks regarding multi monitor setup and vertical synchronization. Wayland is technically usable now on NVIDIA, but not perfected yet.

Nice