Big fan of bash. Pretty sure it’s already installed for you.
This space left intentionally blank.
Big fan of bash. Pretty sure it’s already installed for you.
I look forward to a solution to whatever disease causes people to try and talk to me before I’ve had my coffee.
I dunno, it looks like two framework laptops and a modern macbook pro. They could be doing far worse if that’s what those are.
Good job! ᕕ( ᐛ )ᕗ
You have to pacman -S femboy
first.
We’d constantly get people by telling them holding alt and typing fax would get mirc to give them ops. Usually about a quarter of the channel would drop out.
This is where printf
debugging really shines, ironically.
For files, kebab case. For variables, snake case. For servers, megaman villains.
That is a downside, yes…
A little. If a third party cookie is set while you’re visiting a site, only that site will get the third party cookie back. Multiple sites can have embedded content making third party cookies, and with this change firefox will track where it was made and only give it back there.
With this change, it doesn’t matter if it’s first or third or whatever; cookies will only be given back to a site that matches much of what is in your location bar.
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.
Erectile Encumbrance
Right? I wish they’d respond like this when they themselves fuck up.
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.
Plan? Sure. Cunning? Eh…
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! ☺️
I, for one, welcome our typography as flow control overlords.