An anti-DEI fork by a wingnut and a project that isn’t even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.
… I’m not holding my breath.
Agreed. I was an early Wayland convert because once upon a time I started writing a WM and taking an interest in X internals… And then my face melted off like I’d opened the Ark of the Covenant.
Things are so much simpler now.
I use KDE Connect remote input on Wayland all the time…
KMag is broken (simply has not been updated, not like it couldn’t work) but you can zoom the entire screen in KDE with super +/- is that not good enough?
Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.
It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.
Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.
I have a giant FLAC collection and I sometimes wish I could use these local players because I used Winamp/XMMS/quod libet back in the day, but I feel like I just can’t give up consistent access from outside the house.
I ran Tauon for a while (and have run a few of the others over the years) but I always end up back at my Airsonic setup. Works in any browser, works in a few different Android apps (Subsonic compatible), less of a pain than mpd.
Maybe it’d be different if I was still sitting in front of my computer virtually all the time, but nowadays phone to Bluetooth speaker/car/Chromecast is like 90% of my listening.
Basically, the executing thread might get interrupted in a window of code where the interrupt flags are wrong. Not looking at the specifics, but this could lead to various things from mostly harmless (e.g. potentially holding a lock for many times longer than expected but eventually releasing it) to program crashing (e.g. if taking an interrupt while handling the fault leaves the data structures in an inconsistent state).
This is likely the first one, since it was missed for so long in a very well exercised piece of code.
Are you running the native version or through Proton? When I played Civ VI the Linux native version performed worse than using Proton, ironically. Either way, maybe try switching?
Since you specified multiplayer I’m guessing it’s not time to load from disk or anything.
For ancient stuff, maybe, but AMD is also active in enabling new stuff in the kernel and userspace. AMD basically invented Vulkan, and have had the best open source driver stack for years at this point.
I love what Valve has done for Linux, but it’s the last mile of track at the end of huge amounts of outside work enabling the hardware to work in the first place.
Look on my works Sim Mayor and
I wouldn’t do a mailing list these days, but as someone who spent the early part of my career interacting with devs that preferred this method, it’s actually pretty ergonomic by a 2005 standard. A message thread aware, text based email client that can turn messages into patches in a keystroke makes it actually pretty comparable to modern code review…
I think it’s hard for younger devs to get this because they’re used to email being stuck in a crappy, unthreaded browser interface or Outlook etc. (which are terrible for mailing lists) and most collaboration taking place in code review and chat platforms like Teams/Slack but for decades before these were feasible, email was the way…
Right. GCC -f optimizations are basically like “how hard are we going to try to be clever” and are, I believe, orthogonal to the actual instructions used. Machine dependent args start with -m, like -march or -mavx etc.
I have a few hundred, but 5500? Sheeeit. The game is definitely evergreen though.
Can’t wait for the expansion, 10/21. I’ve been putting off a new play through for it, and Wube always puts in so much polish (as the FFFs show).
So you’re right that this is a bit arbitrary because the line between the standard lib and the language is blurry, but someone writing Rust is going to expect Vec to work, it doesn’t even require an extra “use” to get it.
Perhaps a better core example would be operator overloading (or really any place using traits). When looking at “a + b” in Rust you have to be aware that, depending on the types involved, that could mean anything.
Anyway, I love Rust, it just doesn’t have the 1:1 relationship with the assembly output that C basically still has.
Huh weird, these pull requests just magically accepted themselves
Rust can create native binaries but I wouldn’t call it close to the metal like C. It’s certainly possible to bootstrap from assembly to Rust but, unlike C, every operation doesn’t have a direct analog to an assembly operation. For example Rust needs to be able to dynamically allocate memory for all of its syntax to be intact.
Just hold your ground and keep reading your book, eating alone etc. If someone enters personal territory, shut it down by being honest “I don’t want to talk about that” and move on. Resist peer pressure and be who you are, it’s the same as it was in school.
Also, talk to your coworkers (I know it’s hard) about whether they think it’s appropriate. You have an impression they’re on board with this level of “intimacy” but it’s possible they are just going along to get along.
If persisting doesn’t work then it’s probably time to find another job. Plenty of workplaces out there that just want you to do your job and no more.
HR is definitely not on your side either, unless you can point to specific violations of policy. They exist specifically to cover their own ass, not to actually make your life better.
For XP, the machine KVM presents as may be too new, but that isn’t an issue with non-virtualized QEMU.
Perfect headline.
I’m with you on rejecting AI being sane, but the idea that gaming wikis should be integrated into wikipedia is kinda nuts. If I search “Iron” on wikipedia I’m looking for facts, not a thousand item long disambiguation cluttered with every game that has iron as a resource. Conversely, on a game wiki my search for “Iron” has an entirely different context and I’m looking for different info.
Not to mention game wikis have way lower editorial standards, their own tone (e.g. making jokes), versioning concerns, their own new user friendly homepages etc.
Wikipedia could tuck this all into a separate namespace, sure, but that’s effectively a separate wiki anyway and then it raises questions like “why is wikipedia hosting a mechanical guide for this porn game?” or “How long do we need to host the content for this game that peaked in 2012 and is now abandonware?” that are conveniently sidestepped by those communities supporting themselves.