But it does mean you can spend forty hours a week or thereabouts putting effort into a particular goal and maintaining the knowledge, skills and experience to keep doing it to a high standard without having to sink time and effort into something else in order to get paid enough to live on.
Those forks aren’t maintaining Firefox itself, just their own modifications. If a bug is found in Firefox, the LibreWolf team don’t have to fix it themselves, they can wait for Mozilla to do it, and incorporate the fix once it materialises. There are forks that diverge further, but they either get quickly abandoned after their creator realises how much of a headache maintenance will be, or they’re left with gaping security holes.
When the internet was becoming a world-changing technology, there weren’t thirty years of websites to keep working and malware to protect from, web standards were far simpler, and a much higher proportion of users were enthusiasts who were excited by anything they could get and didn’t mind if things were rough around the edges. Similarly, two brothers could make the world’s first aircraft that flew under its own power, and yet with the combined might of everyone working for Boeing, people are worried about airliner doors falling off and an eight-day space trip has become an eight-month one. Mature technologies need a lot more effort to build and maintain than emerging ones.
Maintaining a web browser in the 2020s is an expensive thing to do. You need full time employees who specialise in all the systems that make up a browser, and can’t leave security-critical parts like ensuring the integrity of the JavaScript sandbox to volunteer hobbyists. It’s far from the only thing Mozilla spend money on, so if they need to mage cost savings, it won’t necessarily stop them being able to maintain Firefox, but another organisation picking it up if they do stop isn’t likely.
If you’re doing things properly, you’ll know your Microsoft account password or have it in a password manager (and maybe have other account recovery options available like getting a password reset email etc.), and have a separate password for the PC you’re locked out of, which would be the thing you’d forgotten. If someone isn’t computer-literate, it’s totally plausible that they’d forget both passwords, have no password manager, and not have set up a recovery email address, and they’d lose all their data if they couldn’t get into their machine.
A lot of the comments are making the assumption that the buttons are telling the truth about being different sizes, but I’ve flushed plenty of toilets where both buttons do a full flush. If you can’t tell the difference after experimenting, it might just be broken or cheap tat.
Is that enough to mitigate how much worse bare Google is than it was ten years ago, back when they were winning against SEO bots? In my experience, it hasn’t been, but I’ve not done enough AI-aided web searches to have a good sample size.
If you give a chip more voltage, its transistors will switch faster, but they’ll degrade faster. Ideally, you want just barely enough voltage that everything’s reliably finished switching and all signals have propagated before it’s time for the next clock cycle, as that makes everything work and last as long as possible. When the degradation happens, at first it means things need more voltage to reach the same speed, and then they totally stop working. A little degradation over time is normal, but it’s not unreasonable to hope that it’ll take ten or twenty years to build up enough that a chip stops working at its default voltage.
The microcode bug they’ve identified and are fixing applies too much voltage to part of the chip under specific circumstances, so if an individual chip hasn’t experienced those circumstances very often, it could well have built up some degradation, but not enough that it’s stopped working reliably yet. That could range from having burned through a couple of days of lifetime, which won’t get noticed, to having a chip that’s in the condition you’d expect it to be in if it was twenty years old, which still could pass tests, but might keel over and die at any moment.
If they’re not doing a mass recall, and can’t come up with a test that says how affected an individual CPU has been without needing to be so damaged that it’s no longer reliable, then they’re betting that most people’s chips aren’t damaged enough to die until the after warranty expires. There’s still a big difference between the three years of their warranty and the ten to twenty years that people expect a CPU to function for, and customers whose parts die after thirty-seven months will lose out compared to what they thought they were buying.
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.
Note: this technique cannot be transferred to single-player games. I have tested the hypothesis thoroughly.
Coal, not oil, but it’s still an interesting fact.
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:
Typically Windows applications bundle all their dependencies, so Chocolatey, WinGet and Scoop are all more like installing a Flatpak or AppImage than a package from a distro’s system package manager. They’re all listed in one place, yes, but so’s everything on FlatHub.
A vote for neoliberals is a vote to not have fascism for four more years. America’s voting system doesn’t allow the never-have-fascism votes to be pooled with the delay-fascism votes, so unless there’s a decent chance for a mass swing of voters from delay-fascism to never-have-fascism, trying to encourage a small-scale swing only makes immediate fascism more likely by weakening the only thing with a chance to delay it.
If the plan is to try and encourage the Democrats to have primaries that actually have the power to move the party left, now is not the time to withhold a vote in protest as there’s a good chance that even if it did convince them, there’d never be another election that wasn’t rigged so they’d lose it no matter how popular they were.
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.
It’s depleted. They’ll just get something like lead poisoning but much worse.
That’s more likely to be the tool assuming it’s running on a case-insensitive filesystem than it is Windows breaking anything. If you mount networked storage running on a case-sensitive machine, that’s something that’s worked fine in Windows for a very long time.