Billegh

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.

Samsonite did. 😥

You need to make sure you buy them from different places, otherwise they might each solve the same problems!

For scale, I need to know how much is an “acceptable” amount…

This is where printf debugging really shines, ironically.

For files, kebab case. For variables, snake case. For servers, megaman villains.

Hey, that’s mine. You can’t have it.

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?

Can confirm; am asshole contrarian.

Octopodeez nuts

FOSS needs more people like you. Thanks for your contributions.

Arch is absolutely divine with its documentation. There is a bit of a “you must be this tall to ride” with them though. Like the tiny [AUR] link. That’s not really well explained, and is even more opaque if you follow the link.

Because Fedora is open source only to the point of it being pathological. If there isn’t am open source driver most time you’re just boned. Someone new is going to have a tough time with it, and the community is on average a very “lol rtfm” bunch. Not as bad as Arch, but that’s not saying much.

Meanwhile, despite the problems around Ubuntu, Debian communities are much more understanding and helpful. Mint even with old packages is going to be an easier time for a newbie. Certainly a newbie unfamiliar with the way entirely too much of the FOSS community is.

It’s fine. I moved to gitlab years ago for 2fa, so while this doesn’t affect me I would be entirely ok with normal 2fa.

It is normal, right? Not a weird Microsoft 2fa requiring their app?