The point is not running Windows or Outlook on a PC in space.
The point is that the Software was not sealed, downloading upgrades while in space, sending telemetry back to Microsoft (or to whoever else).
Those PC are like any other instrument onboard the spacecraft: it's status needs to be known and predictable by NASA.
Not to talk about the amount of unknown and unpredictable extra traffic caused by those PCs onto the "space internet links" which can easily clog any other communication.
And not to talk about smartphones.
This is actually rocket (and space) science, not the horse market fair!
Not just space. There was a time around 2000 or so when US military tanks were running Windows NT and they did what one would expect, BSOD Blue Screen of Death. No idea if that ever resulted in casualties.
Well, it is the other way around actually: NASA should not give a flap about MS tooling, and naturally avoid it completely. Whoever thought of having an Outlook or even 2 out of all the things on there should look for another job, because they clearly cannot be trusted with astronaut lives.
Microsoft beleaguered a federal agency which pretends to be a lot larger than it is (and has a lot of help doing it) with nonresponsive filings. The employees of that agency, FedRAMP, referred to Azure as "a pile of shit" but ultimately approved it anyway.
It's hard to find hard numbers (I looked), but in the "FedRAMP over 10 years" chart partway down in this article FedRAMP themselves claims to have approximately 25 employees, which (I infer prior to DOGE) was augmented to approximately 80 staff with contractors.
It does make a whole lot is sense.
The amount of energy you loose to convert AC to DC can be humongous .
And useless if you produce your own power (normally already in DC).
This. Depending on the project, especially if you're doing something really novel, you can end up going down dozens of dead-ends which, when removed, leave little scars all over the code base.
It can be so refreshing making that decision to open the old code on one screen and a fresh project on the other and do it right from the start.
reply