I know this doesn't address all your concerns, but I switched from Ableton Live to Bitwig Studio for unrelated reasons to my leaving Windows behind, and I was thoroughly pleased with how easy the transition was between the two DAWs (I guess it shouldn't be too much of a surprise given how many ex-Ableton devs work on Bitwig), and how well the Linux build of Bitwig worked. Bitwig on Linux, with Pipewire as the audio engine for low latency operation, is essentially an identical operating experience for me.

Getting your plugins working is a different story. A small but growing number of mainstream audio plugins have native Linux builds available, a wide swath of them work quite well with yabridge (https://yabridge.org/ - so shim to expose Windows audio plugins running in WINE prefixes to Linux audio plugin hosts), and a few required alternatives to be found.

I found the workflow decent enough to use, but as one might expect, some plugins not working well via yabridge/WINE made things a little janky, and once I picked up a Mac device again, that became my production machine. That said, WINE's come a long say since I last tried this out a few years ago, and I'd be interested to see if things work better.

My point, I suppose, is to share a reasonably good success story (though perhaps still not of a grade that you'd be comfortable switching to for paid work), and perhaps to encourage you to consider some alternatives to the tools you use. Tool changes are expensive, sure in cost, but moreso in time, so I don't suggest it lightly. That being said, I think that it might be worth it to grab a Bitwig trial and see how you like it. I'd grab it both on Windows and Linux, so you can try it "how it should work" when your plugins and the DAW are working in harmony while also getting the Linux toolchain working. And from the cost perspective, Bitwig does not have crossgrade licenses, so you can buy Studio once, and run it on any supported platform.

Well, Ableton at least works pretty fine on macOS, if that's more acceptable than Windows for you.

>when this alcoholic is the only one that works properly for the sort of audio and 3D/VFX work

I mean, that seems universally truer than not.

IMHO:

I like the issues faced on Linux more, since I can solve them. I too have a handful of repair scripts.

I feel like an adult to be given access all the internals. I don’t feel that way on Windows (and any other locked down OS).

We should put in the volunteer hours to upstream these fixes to make it nicer for normies :^)

I'm approaching a year now on CachyOS and it has been a wonderful experience. All the games that I play run just fine, maybe a few FPS drop compared to Windows, but it's not a big deal for me. I also don't play any competitive online games that require 3rd party anti-cheat spyware. Biggest positives, I got very comfortable with terminal and CLI work. My development work has definitely improved.

Very few are these days with the enormous amount of resources Valve has been pouring into Proton. The only truly Windows-only games I have encountered were online multiplayer with anticheat and that was almost always because the developer chose not to support Linux (e.g. EAC, Rust) and not for lack of support for Linux.

Perhaps that wouldn't happen if more people switched...

This hasn't been the case for at least half a decade. Most games run perfectly fine if not better on Linux. The only exceptions are purposely broken remote rootkit "anticheat" gsmes which no sane person would want on their system anyway.

This is why I own a playstation

If you need Autohotkey you can still run that under wine (if you are ahk on windows applications), you can run total commander under wine. You can log in as admin I think its time to make the switch

Oh, I also need a way to compile CodeBrowser 4.9 [1]

[1] https://github.com/nilslindemann/Code_Browser_49