• 14 Posts
  • 804 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • The hypothetical says it only goes on for five years, so unless you’re already pretty old, you don’t need to worry about extra risks due to being old. It also said you can get sick days. If you get into trouble, it’s going to be from the ocean rather than because you were unfit for the ocean that day.



  • It’s rare that English children who learn Spanish as the first foreign language that they’re exposed to. If their parents are immigrants, then it’ll likely be their parents’ mother tongue(s), and if they’re not, they’ll likely be taught some French before any Spanish. That can then lead to a habit of saying any foreign word with a French accent.

    Also, England has strong regional variations in accent, so you might be hearing people say exactly the same vowel sounds as they’d use when speaking English, but those vowel sounds might be totally different to how you’re expecting that they’d speak English.






  • AnyOldName3@lemmy.worldto196@lemmy.blahaj.zonerule
    link
    fedilink
    English
    arrow-up
    150
    arrow-down
    18
    ·
    5 days ago

    It’s worth taking a moment to remember that PETA, despite not being perfect, has been the victim of a smear campaign by the meat industry, so every mistake they make is amplified and every policy that isn’t immediately obviously sensible is reframed to look as bad as possible. E.g. you’ll often see that PETA-run dog shelters euthanise a lot more dogs than the average shelter, leaving out the context that plenty of no-kill shelters send all their sick dogs to a PETA shelter to be euthanised so they can claim not to have killed the dog, but that skews the statistics. You’ll also see news reports about PETA abducting a pet dog and killing it, which leave out the fact that it’s one past event being reported over and over as if it’s news each time, and that it was a much more nuanced situation than most people think. A pet dog’s collar fell off while it was unattended playing with a pack of strays, which animal control had been dispatched to round up, and then sent to PETA to be put down, then a series of clerical errors meant animal control told the owners they never had the dog and told PETA that the dog had already been held waiting to see if an owner claimed it, so it was already dead by the time the owners tracked down where it had really ended up.


  • I think you might have misjudged when LCDs became common as by the end of 2004, when Halo 2 released, LCD TVs were already a reasonable fraction of new TV sales, and in parts of the world, it was only a few months later that LCD TVs became the majority. For PC monitors, the switch came earlier, so it was clear CRTs were on the way out while the game was being developed. If they hadn’t expected a significant number of players to use an LCD and tweaked the game as much as necessary to ensure that was fine, it would have been foolish


  • That’s what’s keeping the lights on. If they sunk the extra billions into making their discrete cards genuinely superior to Nvidia’s (which already means taking it for granted that selling comparable products for less money makes them knockoff rather than superior), then Nvidia could stop them recouping the development costs by eating into their own margins to drop their prices. Over the last decade or two, ATi/AMD’s big gambles have mostly not paid off, whereas Nvidia’s have, so AMD can’t afford to take big risks, and the semi-custom part of the business is huge long-term orders that mean guaranteed profit.







  • ECC genuinely is the only check against memory bitflips in a typical system. Obviously, there’s other stuff that gets used in safety-critical or radiation-hardened systems, but those aren’t typical. Most software is written assuming that memory errors never happen, and checksumming is only used when there’s a network transfer or, less commonly, when data’s at rest on a hard drive or SSD for a long time (but most people are still running a filesystem with no redundancy beyond journaling, which is really meant for things like unexpected power loss).

    There are things that mitigate the impact of memory errors on devices that can’t detect and correct them, but they’re not redundancies. They don’t keep everything working when a failure happens, instead just isolating a problem to a single process so you don’t lose unsaved work in other applications etc… The main things they’re designed to protect against are software bugs and malicious actors, not memory errors, it just happens to be the case that they work on other things, too.

    Also, it looks like some of the confusion is because of a typo in my original comment where I said unrecoverable instead of recoverable. The figures that are around 10% per year are in the CE column, which is the correctable errors, i.e. a single bit that ECC puts right. The figures for unrecoverable/uncorrectable errors are in the UE column, and they’re around 1%. It’s therefore the 10% figure that’s relevant to consumer devices without ECC, with no need to extrapolate how many single bit flips would need to happen to cause 10% of machines to experience double bit flips.


  • It wasn’t originally my claim - I replied to your comment as I was scrolling past because it had a pair of sentences that seemed dodgy, so I clicked the link it cited as a source, and replied when the link didn’t support the claim.

    Specifically, I’m referring to

    A single bit flipped by a gamma ray will not cause any sort of issue in any modern computer. I cannot overstate how often this and other memory errors happen.

    This just isn’t correct:

    • loads of modern computers don’t use DDR5 or ECC variants of older generations at all, so don’t have any error-correcting memory. If the wrong bit flips, they just crash.
    • loads of modern computers don’t exclusively use DDR5, e.g. graphics memory (which didn’t have error correction until GDDR7 but can still cause serious problems, e.g. if a bit flips in a command buffer and makes the GPU write back to the wrong address in main memory, overwriting something important), and various caches (SRAM is vulnerable to bit flips from various kinds of radiation, too). If the wrong bit flips, they just crash.
    • Compared to other computer problems that can put the wrong data into memory, like experiencing a bug because a programmer made a mistake, or even just a part wearing out from age, memory errors are really rare, so anything implying normal people need to care is thoroughly overstating their prevalence.

  • That study doesn’t seem to support the point you’re trying to use it to support. First it’s talking about machines with error correcting RAM, which most consumer devices don’t have. The whole point of error correcting RAM is that it tolerates a single bit flip in a memory cell and can detect a second one and, e.g. trigger a shutdown rather than the computer just doing what the now-incorrect value tells it to (which might be crashing, might be emitting an incorrect result, or might be something benign). Consumer devices don’t have this protection (until DDR5, which can fix a single bit flip, but won’t detect a second, so it can still trigger misbehaviour). Also, the data in the tables gives figures around 10% for the chance of an individual device experiencing an unrecoverable error per year, which isn’t really that often, especially given that most software is buggy enough that you’d be lucky to use it for a year with only a 10% chance of it doing something wrong.