• NutWrench@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    ·
    4 days ago

    Every time Microsoft does an update, they reduce functionality. Basic functions like print, search and file storage get moved into sub-sub-sub menus. The point of this is to make room on the main screen for ads. Screwing up your work flow gives you more time to look at them. This is intentional.

    • FauxLiving@lemmy.world
      link
      fedilink
      English
      arrow-up
      35
      arrow-down
      1
      ·
      4 days ago

      You wouldn’t and they didn’t.

      The article has just failed to inform the readers (the few that got past the headline), that this was on his personal Surface Tablet and not on anything associated with the mission.

      • CeeBee_Eh@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        6
        ·
        4 days ago

        If it’s on the ship, it’s associated with the mission. Windows has a very high habit of barfing so over itself, as is evidenced by this article. It’s bonkers to me that they chose to use Windows for anything at all.

        • FauxLiving@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          4 days ago

          The tablets are a convenience, not a requirement and so being commercial off the shelf means it’s cheaper and it works well enough than what purpose-built hardware and software.

          If every tablet died, the mission would proceed without pause. Except the astronauts would be checking gauges instead of looking at a system monitor on their tablet and not sending as many e-mails.

    • amateurcrastinator@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      4 days ago

      There was a slight miscommunication at the fabrication stage. The requirement was to include windows and now they are in a windowless tube with two not functioning outlook accounts. Honest mistake, could happen to anyone

    • abcd@feddit.org
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      4 days ago

      Imagine: You are the first human approaching the moon for a landing since 50+ years. Just a couple of seconds before touchdown the PC starts rebooting because an engineer clicked remind me later on earth and the PC registered that nobody moved the mouse or pressed a key for more than 3 nanoseconds so the user is surely AFK and has definitely nothing important going on so let’s close all open documents and reboot 🤷🏻‍♂️

  • FauxLiving@lemmy.world
    link
    fedilink
    English
    arrow-up
    40
    ·
    4 days ago

    The article leaves out that this was on Commander Wiseman’s personal tablet, a Microsoft Surface Pro and not any device associated with the mission.

    He sought tech support for internet connectivity issues on a PCD (personal computing device), which is a Microsoft Surface Pro.

    The ‘Two Microsoft Outlooks’ was a description of the issue he was having. The headline is implying that there are two machines running Outlook that don’t work.

    NASA detected that the PCD was actually on a network. It asked the commander for permission to connect to the tablet remotely so it could look into a problem with the Optimus software. “I also see that I have two Microsoft Outlooks and neither one of those are working,” Wiseman responded, per a clip shared by Niki Grayson on Bluesky. “If you wanna remote in and check Optimus and those two Outlooks, that would be awesome.”

    The source of the quotes and a better article:

    https://www.engadget.com/computing/artemis-ii-crew-is-just-like-us-needs-help-with-microsoft-outlook-issues-145230968.html

      • tb_@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        ·
        4 days ago

        'cuz they can’t very well send someone over.

        On a more serious note: that’s just the easiest way to go about it? I wouldn’t let my boss remote into my personal machine, but if I were to take it on a mission to the moon that’d be a bit different.

      • FauxLiving@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 days ago

        I guess I should have said ‘and not on any device required for the mission’. The PCDs are personal devices for the individual’s business and convenience.

        They are for things like e-mailing, looking at mission manuals and accessing the Internet. They’re not involved in the operation of the Integrity. All of the mission-critical systems that operate the ship are purpose-built.

        But NASA doesn’t need to re-invent the wheel when it comes to e-mail and PDF reading, so they buy commercial hardware because it’s way cheaper, it works well enough and if it fails it doesn’t compromise the mission.

        • Kjell@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          That makes a lot more sense. When I was reading PCD I was thinking about a private device, even if they don’t have much space and even less time I was thinking that they might bring a few small private things. Like a photo of their family, maybe a book etc.

          • FauxLiving@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 days ago

            On the ISS missions the astronauts have a weight allowance that they’re allowed to take. It may be the same case here.

    • Riskable@programming.dev
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      2
      ·
      4 days ago

      My question exactly: The computers should be purpose-built, including the operating system.

      Why TF aren’t they using something like NASA Linux‽

      If they made it open source you bet your ass they’d get shittons of free support from the global community! If they’re running my software I’d be willing to hop on a call with the command center on any day at any hour!

      “Yes, I know it’s Christmas but NASA is having some trouble with a systemd script on a space ship that’s currently in space…”

      • FauxLiving@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        4 days ago

        My question exactly: The computers should be purpose-built, including the operating system.

        They are, mission critical systems are typically on a Unix/Linux base or completely custom built.

        The systems that use Windows are the ones related to office work, like updating the crew’s bank information and distributing pay.

    • FauxLiving@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      4 days ago

      What the article fails to mention is that this is on Commander Wiseman’s personal Surface Pro and not on any mission-related systems.

  • Arcanoloth@lemmy.ml
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    1
    ·
    4 days ago

    Nice April 1st. I mean that’d be almost as ridiculous as running nuclear subs on Windows, right? Long EOL’d versions at that, eh?

    rustles papers

    Oh.

      • PhatalFlaw@lemmy.world
        link
        fedilink
        English
        arrow-up
        16
        ·
        4 days ago

        On the stream you could very easily see his PIN code being put in, hopefully it’s limited to that device!

        • Pommes_für_dein_Balg@feddit.org
          link
          fedilink
          English
          arrow-up
          8
          ·
          edit-2
          4 days ago

          Of course a submarine’s systems won’t be connected to the internet, but using a Windows base with a “Custom Support Agreement” still gives a private US corporation the power to cripple their subs.
          IMO something so critical to defense should be built by British developers, and based on OpenBSD.

          • gnutrino@programming.dev
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 days ago

            gives a private US corporation the power to cripple their subs.

            You, umm, probably shouldn’t look up who maintains the trident missiles those subs carry…

          • Arcanoloth@lemmy.ml
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            4 days ago

            I agree, but then I’m one of those really hardcore libre-software-only nutcases ;-)

            EDIT: Though, to be fair, the Trident Missiles they carry are US-made, too, so…

          • supamanc@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 days ago

            Further to this, there isn’t a ‘launch the nuclear weapons’ application which controls things. Windows is used for the day to day admin - producing the paperwork required in any organisation - but the actual control systems, for the submarine, the weapons the reactor etc are not running off windows.

          • FauxLiving@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 days ago

            using a Windows base with a “Custom Support Agreement” still gives a private US corporation the power to cripple their subs.

            No, it doesn’t.

            How is Microsoft going to affect the software installed on a nuclear submarine?

            It only gives Microsoft the power to choose to not add new features, the software wouldn’t be on the sub if it required any kind of outside support… the entire point of a nuclear submarine is to perform a second strike after everyone (including Microsoft) is destroyed in a nuclear apocalypse.

            Having software that’s dependent on anything that isn’t on the boat would completely defeat that purpose.

      • FauxLiving@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 days ago

        Most defense systems use some flavor of Unix/Linux.

        Windows is used by the HR person on board to do office work like sending e-mails and updating spreadsheets.

  • me_myself_and_I@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    3 days ago

    In fairness I don’t think Microsoft designed them to work in space. Maybe it’s their internet connection?

  • Brkdncr@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 days ago

    I’m guessing it’s one of two things:

    It could be two shortcuts to outlook. One might actually be Outlook classic.

    Another issue could be a dreaded dual mailbox scenario that occurs when an hybrid on-premises user account gets a mailbox in exchange online before their on-prem account has its attributes created. It’s annoying to deal with and fix.

    I’m curious as to what the issue is and how they fix it. I would assume that latency and bandwidth are a big problem and they have WAN acceleration going on, which can cause some apps to bug out.

    I actually helped Riberbed identify and fix a bug with Exchange optimization that took 4 years to fix. The tech I worked with for about a year when we identified it called me up 3 years later to tell me himself that they fixed and closed it.

    • ITGuyLevi@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 days ago

      Judging by the two Outlooks installed on my cooperate machine I’m guessing Outlook and Outlook (classic) are the two installed… Though they could have “Outlook for Windows” installed too as I see it offering it to me via the Windows store.

      • Brkdncr@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 days ago

        Store Outlook should be the same as Outlook, just with ads if not using a licensed account. I’m not sure how they are handling that, but I know they are trying to kill off all but one of the Outlook versions.