The failure to wait for network-online was the last thing preventing me from going rootless. I am going to have to try this again.

Performance parity? Heck no, not until this bug with the GSP firmware is solved: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538

Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.

…which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that’s why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.

I’ve heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?

Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.

You’re correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they’re slower code paths.

The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.

I’ve tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.

I truly believe the answer to this question is going to be yes around the May - June timeframe when Nvidia releases their explicit sync enabled drivers. All aboard the Wayland hype train babyyyy!

I think there was some bad vibes when they got bought by a less than reputable company a while back. I know a lot of people, myself included switched to Mullvad. I am on Proton now though for the port forwarding.

All of this is still irrelevant. If given the same hardware, one OS performs better than another, then one OS is obviously more optimized…

You’re saying a lot of words but it all just boils down to “throw more hardware at the problem”.

How is this relevant? If an OS performs better on old hardware, it’s still an indication that it is more optimized.

They’re at different layers of the audio stack though so not really replacing.

Well…have you filed bugs for your issues?

Most people have had a very smooth transition over to Pipewire. I have 4 Arch machines and Pipewire has been flawless. I am even using one machine for pro-audio usecases (REAPER, Ardour).

I’ve been using it for years and now I basically can’t live without it. I consider OpenWrt compatibility in all of my router purchases. Currently using a Netgear R7800 and a Belkin RT3200, both are going strong.

It isn’t as widely used because it can be finicky to flash sometimes, and that’s if it’s even compatible in the first place. Even if it works, you may experience a drop in performance unless OpenWrt supports using the routers hardware acceleration features. If there’s no support, OpenWrt basically uses the onboard CPU to do routing and they’re usually not all that powerful.

It’s a native app on Windows and Mac?

You should do it. Easy to setup using either their official AIO image or the community-driven micro service one. I am using the latter and it’s been amazing. It’s completely replaced Google Drive, Calendar, and Contacts for me and with the DAVx5 Android App it feels like a drop-in replacement. I am also using the auto upload feature to back up my photos to it.

Not true. Cumulative updates also take a while, so do the .NET runtimes. Maybe you have a system with a super fast NVMe drive and a new CPU so you don’t realize it, but other OSes can do much more with much less powerful hardware.

Settings and internet are fine. I dunno what to tell you. Very frequently Windows update shows its head, like I’ll randomly want to restart my computer because I installed a piece of software that required it, and then it kicks off a long round updates when I just want to use my computer.

I still think having to leave it on and let it run in the background is still just addressing the symptoms. An update process should be way faster than that so that such a thing isn’t needed.

I turn off modern standby. I don’t want my computer turning on when I am not around or when I am asleep. For laptops, modern standby is famous for turning it on while its in your laptop bag, causing overheating and battery drainage.

I think if an update process is annoying enough to require something like Modern Standby in order to be “seamless”, it needs to be improved.

is a YOU problem.

Wtf is this crap? How is it MY problem when other OSes do a much better job with the update process? You talk about 15 minutes or leaving updates running overnight as if that’s decent. I can do a Linux update within 2 minutes and get my system back up by minute 3. That’s the kind of performance I am expecting and I don’t even need a super fast NVMe drive to do it.

The fact that you’re okay with putting up with Window’s comparatively slow update speed and then have to make excuses for it by saying that the USER needs to constantly baby it or waste power by leaving it overnight is honestly hilarious. To be quite frank, you just don’t know how updates could be better because you’re just used to what Windows has always offered you.

Don’t put the blame on users for a problem that Microsoft can definitely solve but never does.

Most updates on my system are handled overnight, outside the active hours I’ve set in the settings.

Not everyone leaves their computer on draining power. I always put it to sleep when I am not using it. If your argument is that, yeah updates aren’t a problem, you just let your computer run and chew on it for a long time, that’s still a problem…