Billegh

Perl isn’t really any better. There aren’t easy tools that do the same thing as venv. They exist, but they are not easy. Plus there are a much larger amount of cpan modules that have c in them than python.

Yes. Its line noise was of a much higher quality. 😉

Python is the new Perl

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.

At my age, I’d probably rather the onion rings.

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

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

Might? Lol!

I love it. You can’t see me because I can’t see you!

Samsonite did. 😥

PR#5

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

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.

I like the asses on smart people, does that count?

Good, I have a few volume licenses for you then. 🫠

What a tragedy. Would you be willing to accept some of mine? I mean, you already have six now…

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.

They could possibly mean neovim. They appear to have spelled it wrong, though.