NASA's Artemis II Mission Highlights Systemic Reliance on Commercial Software in Space Exploration
Original framing: “NASA did eventually solve Artemis II’s Outlook glitch” — The Verge
The original framing omits the historical context of NASA's reliance on commercial software, which dates back to the 1960s. It also neglects the expertise of indigenous communities and traditional knowledge holders who have developed sophisticated navigation and communication systems. Furthermore, the narrative fails to consider the long-term implications of this reliance on commercial software, including the potential for mission failure and the erosion of NASA's autonomy.
Low structural omission detected in mainstream coverage.
The narrative produced by The Verge serves the interests of the tech industry by framing the issue as a minor glitch, rather than a symptom of a broader systemic problem. This framing obscures the power dynamics at play, where commercial software companies exert significant influence over mission planning and execution. The narrative also neglects the expertise and perspectives of NASA's mission control team and the astronauts themselves.
The reliance on commercial software in space exploration has a long history dating back to the 1960s. During the Apollo era, NASA relied heavily on commercial software for mission planning and execution, which led to several high-profile failures. The current incident is a symptom of this broader systemic problem, which requires a more nuanced understanding of the complex systems at play in space exploration.
The Artemis II mission's Microsoft Outlook issue highlights the systemic reliance on commercial software in space exploration, underscoring the need for more robust and adaptable technical solutions.