Intel graphics support, or the absence of it

That’s like one of the best platforms.

Decent touchscreen support

Pretty much everything on Wayland LGTM. If something doesn’t look quite right (like, hover tooltips), it’s probably the fault of the widget toolkit and will also be broken on Windows.

Windows Ink

As in stylus/pen/drawing tablet? kwin has awesome support, other compositors have some basics.

WSL which I use with NixOS

??? you want a container? distrobox can do that, or something like this

Adobe apps

true… slightly outdated repacks work fine in Wine tho

PowerPoint Libre Impress (…) it’s not even close

Wine.

Gotta love promoting Electron slop like Element right next to stuff claiming sustainability

Despite sleep (the “wake up on every network event” kind of sleep) not being implemented in most PostMarketOS devices, I fucked around with my Redmi and found that the battery lasts much much longer on standby (if I don’t forget to close the apps because they won’t unload themselves)

If you have a whole ass Android container like Waydroid (instead of stuff like android-translation-layer being developed), you can just put MicroG there. Or whole ass Google services, if for some reason you decided it’s a good idea. It’s just Android.

But yeah, hardware support suckzzzz

If your user is in the input group (set up in pretty much every distro), you can use uinput over netcat for forwrading devices (display server agnostic) without extra privileges. Same with the video group. No idea if anyone used this in an actual software suite tho.

display drivers

describes an issue that would be the job of your compositor & window manager

ODF support is in MS Office as well, but if you want to be extra sure you can export as .doc from any office suite (Libreoffice should also tell you if a feature you are using can’t be exported).

“to code”

Hello, this is Linus Torvalds, and I pronounce Linux as Linux

???

Debian separates out stuff with :[arch] suffixes, and is really flexible in the sense that it even lets you install stuff from completely different architectures for, for example, use with qemu userspace. An i386 package is going to only request i386 dependencies, unless it explicitly specifies an architecture, and vice versa. Arch Linux uses the “lib32-” prefix and I don’t really remember how it worked on Fedora but I would imagine something similar. All “gaming focused distros” are merely just their mainstream counterparts with an extra repo for a few packages, it’s not going to change fundamentals.

Maybe the Arch Linux “ports” RFC will finally be of use…

Also, box64 works better in my experience when all of the depending libraries are installed properly, and they are guaranteed to be there in this scenario given that there’s the Steam runtime.