It’s been the default since 2015 when Windows 10 launched, although there was an obvious button to opt out during first-time setup back then which was then respected permanently. It’s got gradually less prominent over time, and maybe the article’s just doing a really bad job of explaining that it’s no longer something where your initial preference is permanent and it’ll change back to the default every so often.

It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.

!openmw@lemmy.ml has less than 150 subscribers, so it’s definitely not large. We’re already swamped with infrastructure work for the stuff we already self-host, so I don’t think we’ll be running our own Lemmy instance any time soon.

OpenMW’s official Lemmy community has been on lemmy.ml since 2021, way before lemmy.world existed (and most other instances, too), and way before there was any inter-instance drama. It’s becoming increasingly likely that it’s not going to be a suitable long-term home, but we’d be much happier if we could migrate the existing community rather than start from scratch with a new one. Is there any way to do that yet?

It doesn’t necessarily work that way, though. If tests tell you you broke something immediately, you don’t have time to forget how anything works, so identifying the problem and fixing it is much faster. For the kind of minor bug that’s potentially acceptable to launch a game with, if it’s something tests detect, it’s probably easier to fix than it is to determine whether it’s viable to just ignore it. If it’s something tests don’t detect, it’s just as easy to ignore whether it’s because there are no tests or because despite there being tests, none of them cover this situation.

The games industry is rife with managers doing things that mean developers have a worse time and have the opposite effect to their stated goals. A good example is crunch. It obviously helps to do extra hours right before a launch when there’s the promise of a holiday after the launch to recuperate, but it’s now common for games studios to be in crunch for months and years at a time, despite the evidence being that after a couple of weeks, everyone’s so tired from crunch that they’re less productive than if they worked normal hours.

Games are complicated, and building something complicated in a mad rush because of an imposed deadline is less effective than taking the time to think things through, and typically ends up failing or taking longer anyway.

I think you’re reading things into my comment that I intentionally didn’t put in it. I’m just making the point that games already don’t get to control the amount of hardship the player experiences because some players start out better than others, and some improve faster than others. If a game has a fixed difficulty level, there’ll always be people who find it easier than the developers intended, and people who’d still be unable to finish it with thousands of hours of practice (and plenty of people will play for ten or twenty hours before deciding they don’t have time to find out if they’d eventually get good enough). On the other hand, if a game’s got several modes, then there’s a good chance a player will pick a difficulty level that’s too easy or hard for them, so it could make the problem worse, but, critically, it wouldn’t be what introduced it in the first place.

Regarding your point about Animal Farm, it’s a bit more like deciding not to read an encrypted copy of the book. It might be a trivial Caesar cipher that could be easily broken, and you could be reading about some animals being more equal than others in a few seconds, or it could be modern AES that can’t be broken before the heat death of the universe, or it could be anything in between. If you don’t quickly make enough progress to see that you’re actually going to get to read it, then you’ve no way to know whether it’s seemingly insurmountable or literally insurmountable.

If someone’s saying they don’t have time to get good at Dark Souls, they’re agreeing with you that not everything has to be for everyone, and they’ve decided that Dark Souls isn’t for them. They don’t have to be happy about that, though, especially if they’ve had to pay for the game to find out.

Different people have different skill levels, so will experience different levels of hardship. Someone who’d played every Dark Souls game ten times (which isn’t that rare) would find Elden Ring much easier than someone who’d never played a soulslike before. If the difficultly could be scaled to normalise for that, then everyone would have a more consistent experience closer to the intended one. It’s probably not remotely practical to achieve that in every case, though.

It’s a 250W+ part running at around 1V, so it’s going to draw a lot of current. Power is supplied via many pins on the back of the CPU, and they’re connected to many traces, so it’s not putting all that current through just one. It still puts out a lot of heat anyway, which is why modern motherboards have large heat sinks, sometimes with fans, on their VRMs.

Yeah, the Wayback Machine doesn’t use Reddit’s API, but on the other hand, I’m pretty sure they don’t automatically archive literally everything that makes it onto Reddit - doing that would require the API to tell you about every new post, as just sorting /r/all by new and collecting every link misses stuff.

The archive sites used to use the API, which is another reason they wanted to get rid of it. I always found they were a great moderation tool as users would always edit their posts to no longer break the rules before they claimed a rogue moderator had banned them for no reason, and there was no way within reddit to prove them wrong.

If things are done according to the spec, the logo’s engraved/embossed on one side and not the other, so you can learn to feel that and get it right first time even in the dark.

Sounds like you’ve got some Dells with USB ports, and some Dells with off-spec not-USB ports.

Shared components work brilliantly in a fantasy world where nothing uses new features of a library or depends on bug fixes in new versions of a library, and no library ever has releases with regressions or updates that change the API. That’s not the case, though, so often there’ll exist no single version of a dependency that makes all the software on your machine actually compile and be minimally buggy. If you’re lucky, downstream packagers will make different packages for different versions of things they know cause this kind of problem so they can be installed side by side, or maintain a collection of patches to create a version that makes everything work even though no actual release would, but sometimes they do things like remove version range checks from CMake so things build, but don’t even end up running.

It says few opposite of that, i.e. to try the webapp in Microsoft Edge or Chrome, or use the desktop app.

Not that I agree that removing/banning archive links is sensible, but reddit has a much bigger budget for lawyers than any instance admin, so is in a much safer position with grey-area and black-area-but-no-one-complained-yet content. It’s not like reddit was ever particularly anti-piracy, either - the corporate interests they bowed to were advertisers and their shareholders.

The way I like to think of it is that non-copyleft licences are like giving everyone freedom by saying there are no laws - suddenly, you can do anything, and the government can’t stop you! However, other people can also do anything and the government can’t stop them, either, and that includes using a big net to catch other people and make them their slaves. The people caught in the nets aren’t going to feel very free anymore, and it’s not unreasonable to think that a lot of people will end up caught in nets.

Copyleft licences are like saying there are no laws except you’re not allowed to do anything that would restrict someone else’s freedom. In theory, that’s only going to inconvenience you if you were going to do something bad, and leaves most people much freer.

The idea is basically that you shouldn’t be able to restrict anyone else’s freedom to modify the software they use, and if you’re going to, you don’t get to base your software on things made by people who didn’t.

Usually FOSS is specifically copyleft licences like the GPL, which Microsoft don’t use. Their open-source stuff tends to be MIT.

I’ve read that part of why GIMP is the way it is is because it’s meant to be a testbed for the GTK UI library, so features are added to use new UI elements as much as they are to aid photo manipulation, and in some cases it’s considered preferable to use a weird widget so it’s got a test case rather than whichever widget leads to the best UX. I don’t think I’ve ever looked for a more definitive source than a Lemmy/Reddit comment, but it’s at least consistent with my experience of using GIMP.

I could scare people by mentioning that with OpenMW, our release process for 0.48 has been ongoing for eleven months as people keep finding release-blocking issues in our RC builds. Maybe we’ve just barely started waiting for the next release of Lemmy, and just don’t know it.

There is only one photo. The left pair of sockets is upside down.