Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitates it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social but created this profile on kbin.run during the first week-long outage.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 64 Comments
Joined 5 months ago
cake
Cake day: June 4th, 2024

help-circle
  • (FWIW the downvote wasn’t me)

    That sounds like you’re suggesting that Microsoft wouldn’t care what was installed locally to be able to net-boot / run the rest of Windows.

    I think it’s all but certain that they’d want user’s computers to to boot into something they made, or at the very least, slapped their branding all over, even if that was only a wrapper for their web browser.

    I can definitely see them going down the line of saying that their online apps aren’t guaranteed to work under any other system, going so far as to throw in a few deliberate stumbling hazards for anything that isn’t theirs. (Until anti-trust, etc.)

    And thus, dual booting will still be something that people do. Even if - as you clarified - they’re not going to cripple that as well.


  • The only way to prevent dual booting would require a UEFI/BIOS that pulls the OS straight over a network, bypassing local storage entirely.

    Even if that didn’t already rule it out, the size that OSes are these days makes it even less likely. At least not unless Microsoft (or whoever) are planning to ditch absolutely everyone who doesn’t have gigabit internet. (It would be kind of funny for an OS to go back to being 1990s-sized to mitigate that though. And funnier still when someone inevitably captures it onto a hard disk anyway.)

    A more likely vector would be to deliberately break third party bootloaders every time Windows boots. And that would last until the next anti-trust / monopoly lawsuit and they’d roll it back to the current behaviour of only breaking third party bootloaders on installation.

    And even if somehow that didn’t get rolled back, just wait until hardware vendors introduce this thing called a “switch” that can be added just before the power connector on an SSD. Can’t boot from a drive that has no power. BIOS defaults to the next SATA channel. And now you’re booting into Linux.

    Doing the same for a mobo-mounted NVMe drive is harder but not impossible.

















  • To be fair, quite a lot of work was done to ensure that things didn’t go wrong when the year changed over, and some things still did go wrong (and still do if you know where to poke), but thankfully there weren’t any globally affecting ones. Mitigations were in place in plenty of time. I can’t recall any specific tragedies, but I would be surprised if there wasn’t a handful of those.

    More humorously, many, many websites started the new year with their auto-generated year showing as 19100, because no-one thought to fix that.

    32-bit time / the 2038 problem is a similar kind of deal and steady work has been under way probably since Y2K was cleared.

    So yeah, we do need to get ahead of the technology (AI this time) like we do with everything else, but we shouldn’t get too worked up about it because the experts have things under control.

    Right…?


  • palordrolap@kbin.runtoComic Strips@lemmy.worldBe nice
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    4 months ago

    Listen, we’ve had some absolute monsters who were, regrettably, human almost manage that feat. There’s no reason not to assume that a robot of similar mindset might not actually manage to do it.

    “Run it better than we do” is then laid bare as the subjective nightmare it really is. Sure, some people will like it, but we have a name for those: Masochists.