Given the usual quality of BIOS/UEFI option descriptions it’s remarkably close to being sensible. I would’ve expected something like “enables limiting CPUID maximum value”.

Oh, don’t get me wrong, I fully agree. Undefined behavior is terrible UX and a huge security risk.

Undefined behavior was kind of okay when RAM and storage were measured in kilobytes and adding checks for this stuff was noticeably expensive. That time has passed, though, and modern developers have no business thinking like that, even ones working on low-level languages.

I should’ve phrased my comment differently.

My girlfriend has this when she plays Palworld. She switches between two of my computers to do so and on both Palworld will start thinking it has the full screen while the menu bar is still present.

Usually, alt-tabbing out and back in helps, as does using alt + enter twice.

Oddly enough, I don’t get this behavior on either computer so it seems to be connected to something user-specific.

Yeah, that’s basically the kind of logic you use when designing a low-level programming language: If we didn’t define what happens here then anything that happens is correct behavior and it’s up to the user to avoid it.

Of course applying that logic to a GUI application intended for a comparatively nontechnical audience is utter madness.

That one’s easy. Is the crash part of the program’s design?

If not: It’s an implementation bug, the program is not behaving as intended.

If yes: It’s a design bug, crashes shouldn’t be intended behavior.

Oh, please don’t take that remark as an excuse or endorsement. The intended tone is one of resignation – pseudonymity reduces the social cost of bad manners to near zero and there’s not much we can do about it.

I will forgive people for being blunt in their criticism, however. High-ranking politicians are exactly the people who have to be able to take a certain level of verbal abuse since their decisions can change other people’s lives in directions that justify the liberal use of expletives.

Which plays back into my perception that Fetterman is currently not suited to his role.

I can understand both sides here.

On the one hand I have empathy with him like with any victim of such a life-altering injury and wish him a swift and full recovery. I don’t want people to suffer and, quite frankly, “the brain doesn’t work right anymore” is one of my personal horror scenarios.

On the other hand this kind of behavior is a huge problem in someone capable of making decisions that can alter the lives of other people – millions of them, in this case. He has enough power to ruin a lot of people’s lives, intentionally or not.

Even as someone who isn’t impacted by his mental fitness in any way, I’d agree that removing him from office seems like a good move. That man needs rest, not the stress of a high-profile political office during interesting times. And his state needs someone with a level head, which doesn’t mesh well with a semi-recent traumatic brain injury.

And, well, this is a politics community so guess which part the discussion will focus on. (Also, this is online so people are inclined to be assholes.)

Well, the camera needs to talk to your onsite storage in order to store video. A simple consumer device like a Ring isn’t going to be hardwired; it just uses Wi-Fi (which every household can be assumed to have) to connect to your LAN and talk to the storage device.

The question is why the Wi-Fi could be turned off on the first place. Probably an ISP-managed router; I doubt they’d go and jam the entire spectrum between 2.4 and 7 GHz.

That’s one reason why people should use their own router and/or access point whenever possible.

One problem is that in a world without major problems, stakes have to be low (which is perfectly fine and can make for an engaging story) or an external threat has to be introduced. The latter can easily feel forced or disconnected with the world.

I wonder how it would be to have a nonlinear game set in two time periods. One is a solarpunk-ish idyll under threat (with the protagonist’s actions focused on protecting it) and the other is a preceding industrial dystopia (with the protagonist’s actions focused on effecting change for the better).

Throughout the game the player first learns that the dystopian protagonist’s actions did succeed in changing the world for the better but also that the threats faced by the idyllic period are consequences of those actions. The message is that even ideal decisions can have negative effects down the line, “happily ever after” endings don’t really exist, and happiness requires maintenance. Yet, change for the better is both possible and worth the effort.

I do but my condo’s HOA is more concerned with building maintenance than with telling people what to do. Our regulations fit on a single A4 page with a fairly large font size.

Now, a neighborhood HOA would probably be a different beast altogether.

Or they’ll do Elden Ring 2 with GoW gameplay as a live service game because surely people just want a new but proven IP.

Good point. If you look at the Yakuza games, they’re typically set in a little entertainment district. The map isn’t huge but it’s not supposed to be. It feels the correct size for a busy little part of town.

Meanwhile, yeah, Fallout 3 gave me the impression that even before the war the DC metropolitan area was home to maybe a thousand people.

If you use a .local domain, your device MUST ask the mDNS address (224.0.0.251 or FF02::FB) and MAY ask another DNS provider. Successful resolution without mDNS is not an intended feature but something that just happens to work sometimes. There’s a reason why the user interfaces of devices like Ubiquiti gateways warn against assigning a name ending in .local to any device.

I personally have all of my locally-assigned names end with .lan, although I’m considering switching to a sub-subdomain of a domain I own (so instead of mycomputer.lan I’d have mycomputer.home.mydomain.tld). That would make the names much longer but would protect me against some asshat buying .lan as a new gTLD.

And that’s one of the annoying things about snap: It’s fundamentally a nice system with neat capabilities but it’s spoiled by Canonical’s proprietary backend.

But it’s still not a backup strategy. You should always have a second partition on the server that you sync your data over to. For performance reasons this partition should be on the same RAID 0 array.

There is one metric where Intel is better and that’s Thunderbolt. You typically get more full-featured Thunderbolt ports with an Intel CPU. Of course whether that point is relevant is highly dependent on your use case.

Oh yeah, the equation completely changes for the cloud. I’m only familiar with local usage where you can’t easily scale out of your resource constraints (and into budgetary ones). It’s certainly easier to pivot to a different vendor/ecosystem locally.

By the way, AMD does have one additional edge locally: They tend to put more RAM into consumer GPUs at a comparable price point – for example, the 7900 XTX competes with the 4080 on price but has as much memory as a 4090. In systems with one or few GPUs (like a hobbyist mixed-use machine) those few extra gigabytes can make a real difference. Of course this leads to a trade-off between Nvidia’s superior speed and AMD’s superior capacity.

These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.

We used to have one: “Solang das deutsche Reich besteht wird jede Schraube rechts gedreht.” (“As long as the German Empire persists every screw is turned right.”)

Given that the German Empire failed spectacularly, this sentence isn’t very popular anymore.

They did PR campaigns against Linux and OpenOffice for quite some time – until cloud computing took off and it turned out they could earn more money by supporting Linux than by fighting it.

In fact, Microsoft weren’t happy about FOSS in general. I can still remember when they tried to make “shared source” a thing: They made their own ersatz OSI with its own set of licenses, some of which didn’t grant proper reuse rights – like only allowing you to use the source code to write Windows applications.