Billegh

I’ve found that arch is often an easier time than fedora if you want “up-to-date” Linux. Fedora has its heart in the right place, but its pathological adherence to open source makes it sometimes a very difficult time for certain classes of new things.

But as I have opinions as to my lawn and your location relative to it, Debian is more often fine for my needs. It’s my daily driver on pretty much everything at work and at home, with the exception of a few arch and fedora systems in my home lab.

I, for one, welcome our typography as flow control overlords.

Big fan of bash. Pretty sure it’s already installed for you.

Samsonite did. 😥

Jia Tan is at it again!

Fact. An unfortunate one, but still a fact.

Train an LLM on your code and share the model.

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

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.

Could? Lol.

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.

That’s fine. The post I was responding to mentioned the one I mentioned though, so nyaaa.

Codium runs just fine in xterm.

It displays elsewhere, sure. But it runs there just fine.

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.

x-mail, huh