It wasn’t me who you replied to originally - I agree that it’s most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they’ve had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.
You’ve misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they’d be delaying the release date, and that new release date is after the microcode update.
Yes. Every time, it’s gone less well than opening a banana from the stem end, unless the banana was horrendously underripe. I’ve never had the problem the alternative approach is claiming to fix unless I’ve intentionally opened the banana badly on purpose to prove a point about the problem really being people opening from the stem end incompetently.
A) The peel becomes easier to tear faster than the inside gets softer. You don’t need to snap it, it doesn’t need nearly enough tension to count as a snap once it’s ripe.
B) The banana’s been selectively bred to want to be as delicious as possible. It only wants you to be happy.
Bananas are the way they are through millenia of selective breeding, so there’s no reason to think that monkeys know anything we don’t. If pinching the bottom is easier than bending the stem, your banana isn’t ripe yet and doesn’t want to be eaten until later.
Installing hidden cameras in a public toilet is harmless by that definition as long as they never get discovered, but would still be highly immoral. I don’t think you’ve thought this through. People’s right to decide what happens to their body extends to things like who can see it rather than just who can physically touch it.
It’s at least common on forums as bots love making accounts with non-megacorp email addresses on PhpBB and MyBB forums. Typically, there aren’t people signing up the same services with business emails as personal ones, so if ones expecting not to be used by businesses want to fight spam, it’s generally pretty effective and consequence-free to block email providers not known to have effective anti-bot measures built in.
That would be annoying for people who work on files with a double extension for legitimate reasons, e.g. .tar.gz, and (this can’t be stressed strongly enough) Windows users do not pay attention to warning popups, so it wouldn’t actually help. Despite it being eighteen years since Windows Vista released, and therefore vanishing unlikely that any given software was written assuming that Windows didn’t have a permissions system, it’s still most people’s first troubleshooting step to try and run things as admin, and you still get loads of people (including ones who should know better, e.g. ones who also use Linux and would never log in as root) who disable UAC as one of the first things they do when setting up a windows install, and end up running everything as the equivalent of root just to suppress the mildly annoying pop-up when something asks for elevated permissions.
So, your proposed popup:
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.
No, but mostly you.
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?
Either: