Hurd?

Honestly, it’s still the F310 for me. I have mine since the early 2010s and it’s still working perfectly. Those things are built like tanks and between XInput and DirectInput are compatible with just about any PC game of the last forty years, no extra software required. Also, they’re dirt cheap.

Honorable mention to the F710, the wireless version. While Windows 10’s USB stack unfortunately broke compatibility with it (causing randomly dropped inputs), Linux does not have that problem.

In my experience rear-mounted sensors are the most accurate, closely followed by under-screen sensors. Side-mounted sensors are utter garbage.

Accuracy isn’t even that much of an issue, it’s that the side-mounted ones are far too easy to accidentally trigger just by handling the phone. I can’t count the number of times my last two phones told me I had three incorrect fingerprint attempts after I had just pulled them out of my pocket.

Then I got a Pixel and I have no more such issues and virtually perfect accuracy. Same on a Samsung tablet. Same on an old phone I had where the power button was on the rear and had a full-size sensor.

Basically, I’m perfectly happy with any front- or rear-mounted full-size sensor. Those tiny side-mounted ones suck.

The Crucial P3 series is QLC-based, which I’m not a huge fan of because your performance is strongly dependent on the SLC cache. (Also, early QLC had endurance issues but no idea if that’s still the case.) I’d go with a TLC-based SSD if it doesn’t break the budget.

Other than that it looks like a decent build. Should perform well with Linux.

It happens on Linux – after your package manager has updated Firefox. Which typically means that you told it to. So it’s not really a surprise.

Oh, right. Fast Boot. I forgot about that bundle of joy.

But that’s wasn’t the only instance of an NTFS volume suddenly being broken. Another favorite was when I shrunk a volume on one disk from Linux (and then remembered that Windows correspond done it better) and rebooted to have it fixed and Windows proceeded to repair one on a different disk.

NTFS feels rock solid if you use only Windows and extremely janky if you dual-boot. Linux currently can’t really fix NTFS volumes and thus won’t mount them if they’re inconsistent.

As it happens, they’re inconsistent all the time. I’ve had an NTFS volume become dirty after booting into Windows and then shutting down. Not a problem for Windows but Linux wouldn’t touch the volume until I’d booted into Windows at least once.

I finally decided to use a storage upgrade to move most drives to Btrfs save for the Windows system volume and a shared data partition that’s now on ExFAT because it’s good enough for it.

I’m not sure about the SSD. Has QLC substantially improved since hitting the market? If not I’d recommend going with something TLC-based.

That’s why they’re on the plane; they’re working overseas.

When I debugged my crackling sound I followed various advice that said to enable 44100 in addition to 48000 and it fixed nothing. Then I disabled 48000 and it worked because the auto-switching refused to work. (And of course the other computer runs the same games just fine on 48000 because things can’t ever be simple.)

That’s why I mentioned it.

Try setting the rate to 44100 and only that, no double rate support; most games try to output at that rate and don’t deal well with being upsampled to 48000.

Useful stereotypes can help a person avoid danger.

Unknown mushrooms don’t have to be poisonous but being careless with them can lead to a grisly death. Drivers don’t have to be unaware of me but it takes just one who is to put me in mortal danger if I’m not careful. A man following a lone woman at night where nobody else is around doesn’t have to have ill intent but she’s still better off being prepared for the case that he does.

Does this discriminate against mushrooms, drivers, and men? Yes, but that’s the point. It’s essentially an informal safety guideline and it deliberately overreaches just like real safety guidelines. The 999 times someone doesn’t need that handrail don’t outweigh the one time they do; not in OSHA’s eyes. Because someone might die if the handrail fails that one time.

This whole thing becomes problematic when it gets over-applied. Avoiding canned mushrooms in the supermarket won’t protect me from poisoning. Assuming that all drivers are blind and irresponsible will not improve my behavior on the road. Being afraid of all men in all situations will not make that woman’s life better.

Like always, Paracelsus is right: The dose makes the poison. (And like with poison, some stereotypes are so toxic that any dose of then is bad for you.)

Thanks. The pain is very moderate for me but yeah, there’s layers to how uncomfortable it is. Still totally worth it.

Nose surgery to remove polyps and correct a septum deviation. I’m getting out of the hospital today. It’s going to take a few weeks for me to fully heal but being able to breathe through the nose again is luxurious.

I gotta be honest, I haven’t used a dedicated sound card since the Vista/7 era when EAX stopped being a thing and onboard sound could handle 5.1 output just fine. The last one I had was a SoundBlaster Audigy.

These days the main uses for dedicated sound interfaces are for when you need something like XLR in/out and then you’ll probably go with something USB.

Port 220.

IRQ 5, port 220h, DMA 1 was what I used for my SoundBlaster 2.

Later I used IRQ 5, port 220h, DMA 1, high DMA 5 for my SoundBlaster 16.

Why not go straight for the Ultimate Warrior, get him in a debate with Trump, and make the host cry?

Thunderbolt 3 is part of USB4. Thunderbolt 4 is separate and not supported by AMD processors yet, probably due to licensing issues. (Note that prior to USB4 this was why Thunderbolt 3 wasn’t available on AMD.)

The one advantage Intel has is Thunderbolt 4. Few people care about Thunderbolt on a desktop but on laptops it’s kinda nice (when it decides to work).

Besides, LLMs struggle with retaining contextual information for long and they’re pretty dang resource hungry. Expect a game with LLM-driven dialogue to reserve several gigs of VRAM and a fair chunk of GPU processing power solely for that.

And then you still get characters who hallucinate plot points or suddenly speak gibberish.