Would have switched years ago if it wasn't for Adobe. Open source equivalents to Photoshop and Lightroom are NOT viable alternatives

For casual use I use lightroom web and it's good enough for me, if you haven't tried it, I highly recommend.

I'm sure for some workflows it isn't sufficient but for basic edits and raw development it works quite well.

Yeah, i use online LightRoom for checking images in the darkroom actually, but for serious use, the old desktop app is still king. There are alternatives, like the excellent Capture One, but none available on Linux. I could live without Photoshop, but not Lightroom or similar.

Not really equivalent to Lightroom, and not remotely a replacement, but there's Corel AfterShot Pro [1] (source: about 15 years ago, I was one of the (1?) proud Linux users of Bibble 5, its predecessor)

[1] https://en.wikipedia.org/wiki/Corel_AfterShot_Pro

ALVR has been working really well for me on my Quest 3.

there are a lot of other things stopping people from migrating besides gaming though. sure, there are alternatives for professional audio/photo/video editing/producing, but they all mean losing some functionality if you migrate.

Don't use NIC name for networking. This is a none problem.

It is clearly a problem for them. Just because you do something different doesn't invalidate their pain point

A known problem?

This is an ignorant response. It is 2026. The OS shouldn't be storing network configuration by nondeterministic device name when I ask the OS's default network management tool to join a wifi network.

I was under the impression that the systemd device naming schemes were created specifically to solve the problem you describe[1].

Are there cases where the old scheme worked well that none of the systemd schemes properly address?

Is the scheme Windows uses to bind configuration to physical network interfaces even documented?

[1] https://systemd.io/PREDICTABLE_INTERFACE_NAMES/