It’s much more… manual than others, I’ll admit. For me anymore it’s a labor of love.
This space left intentionally blank.
It’s much more… manual than others, I’ll admit. For me anymore it’s a labor of love.
Slackware: because I’m old and arch is too trendy.
I normally use rm
for that. Or wipefs
if I’m feeling particularly spicy.
Yes. I prefer my os to be more passively adversarial. Like Gentoo. It hates everything equally.
end users have to deal with it either way
So, normal linux shenanigans.
There are ways to do it, buy per the EULA all are not allowed.
You should still do it. But be aware that you aren’t supposed to.
Delightfully, I was unaware.
I wasn’t comparing badness or abuse, I was comparing autonomy. In the US they have the option to use the legal system to fight against things they don’t want to do. Usually ineffective, sure. But the option is there. Not so in China.
No, but a “company” in China has far less autonomy from the government in China than one in the US. For some people, that can be stressful
I, for one, welcome our typography as flow control overlords.
Big fan of bash. Pretty sure it’s already installed for you.
This is where printf
debugging really shines, ironically.
For files, kebab case. For variables, snake case. For servers, megaman villains.
They really did do a good job. The difference is that they have access to documentation about Linux that wine doesn’t have about Windows.
Because Wayland is fundamentally very different from the older X protocol, and many programs don’t even directly do X. They leverage libraries that do it for them. Those libraries are a huge part of the lag. Once GTK and Qt and the like start having a stable Wayland interface, you’ll see a huge influx of support.
A big part of the slowness is why Wayland is a thing to begin with. X hid a lot of the display hardware from apps. Things like accessing 3d hardware had to be done with specialized display clients. This was because X is natively a remote display tool. You can use X to have your program show its display somewhere else. Wayland won’t do that because that’s not the point. Applications that care will have goals for change. Applications don’t care will support it once someone else does it for them.
Right now, the only things that would benefit from Wayland are games and apps that make heavy use of certain types of hardware. Half of those don’t care about linux, while the other half is OK with X and xwayland.
I feel all of that. Debian is painfully slow to bring up-to-date, and all of Arch is neurotic.
You might have a better time with Fedora as they are closest to Wayland, but Fedora is pathologically open source to the point that if there aren’t open source drivers for a thing you’re triple tucked…
Gaming on linux has been, still is, and always will be a struggle. I hope you give it a try again in a year or so. I personally use Debian as my base system, with an Arch VM on CPU and GPU passthrough for work and gaming. You’ll get there eventually! ☺️
Which distro were you using?
Let’s be honest: nearly all of them now are windowslike girly distros…