AnyOldName3

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’ve swiped to upvote on occasion, but I’ve accidentally triggered both it and replying while trying to scroll fast more often. I think it’s really just a matter of being fat too keen to activate off motions that mostly go up or down, and until it’s not in the way of scrolling, there’s not any way to reliably judge how good it’d be if it wasn’t.

If the AI had any actual I, it might point out that the most recent Halloween Document was from twenty years ago, and Microsoft’s attitudes have changed in that time. After all, they make a lot of money from renting out Linux VMs through Azure, so it’d be silly for them to hate their revenue stream.

I’d be unsurprised if it’s just set up to abandon the conversation if accused of lying, rather than defending its position.

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.

The legalese in the US (which might as well be everywhere as you need to have compatible copyright with the US to have a trade deal with the US, and your country is in trouble if it doesn’t have a trade deal with the US) is basically that:

• If you buy a physical copy, you’ve become the owner of that one copy of the IP contained within. As the owner of that copy, you can do stuff with it like read it, display it, destroy it, or sell it on to someone else thanks to the First Sale Doctrine (but you can’t do other things like copying it, unless it’s a DVD as there’s a specific exemption for the copy your DVD has to make to RAM in order to decode the DVD). There’s nothing the copyright holder of the original can do to stop you exercising these rights.
• If you buy a digital ‘copy’, you’ve not bought a copy, you’ve bought a licence to use one of the publisher’s copies that they’ve given you permission to have on your device(s). They’ll also have given you permission to do things like read it if it’s an ebook or play it if it’s a video game, but as it’s their copy, not yours, you don’t automatically get rights to do anything they’ve not explicitly permitted you to, and it’s not in their interests to permit you to sell it on unless they think you’ll pay enough more for a resaleable copy that it covers a potential future lost sale.

I’m sure plenty of publishers would love for the second set of rules to apply to things like books, and from a quick googling, it seems like occasionally academic textbooks have included a licence agreement instead of you actually owning the physical book, but I imagine that most publishers are concerned about bad PR from attempting this with a hit novel and also don’t want to be accused of fraud for having their not-a-book-just-a-licence on the shelf next to regular books and thereby tricking consumers into thinking they were buying a regular book. EA attempted to double-dip over a decade ago with Battlefield 3, which included a copy of the game (with regular First Sale Doctrine rights) and a licence key for the online pass (which wasn’t transferrable) and got bad press because of it. Newer PC games often come as a key in a box with no disk or a disk that only runs a web installer, so you’ve not got a copy of the game to claim you’ve bought and obviously only have a licence, and this seems to have caused less upset. This wouldn’t work with a book, though, as you have to fill in the pages at the printing factory, and can’t magically do it only after the user’s got it home.

Again, you’re reading things into my comment that I specifically avoided saying. If perfect, good and mediocre can’t exist, then obviously what I said isn’t applicable, and you shouldn’t be applying it in that context. It’s just like you wouldn’t reply to a post about it being necessary to outlaw the slavery of elves by saying elves are fictional and the author is demonstrating that they’ve not considered this.

This segues nicely into my original point - if you try applying adages to situations they’re unsuitable for, dumb things will happen.

I didn’t, otherwise I’d have said bad was always better, which would be silly. It’s pretty reasonable to assume that most of the time, at least one of the perfect, good or mediocre solutions would be actually achievable, so settling for a just barely tolerable one would be unwise if it was going to block one of the better solutions happening later.

Anyway, my main point is that people have a tendency to bring up the perfect being the enemy of the good when the thing people were objecting to wasn’t even good, and a better solution would be perfectly feasible.

The perfect, good, mediocre, and just barely tolerable are all enemies. Sometimes bad is better as it doesn’t erode the motivation to solve the problem and means you’re more likely to end up with a good solution later. Often, when people accuse others of letting the perfect be the enemy of the good, the option was neither perfect nor good, just mediocre or barely tolerable. The exception is when one solution can go on to evolve into a better one, but it can still be better to wait until it does before deploying it.

I’m not convinced this is exactly applicable to the story in the OP, though. The compromise would have eroded the motivation to vote for the original legislation in that election, but probably made it more likely that it could have happened in the next one, and made the consequences of putting it off that long slightly less bad.

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.

Have you set up linear advance/pressure advance? I found it worked wonders with making sure the extruder gets back up to pressure after a retraction.

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.

You’re not going to be able to do an FDM print without there being layer lines and without there being a plane in which the part is more fragile thanks to layers being easier to delaminate from each other than to break. A resin printer can more or less avoid these problems, but you’ll need an expensive engineering resin to get the same strength. None of the problems affect everything you might ever want to make, though, and there are plenty of things you might only want one or two of, so obviously would never machine a mould for.

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