Big takeaway for me is that the reentry and “landing” of Ship looked great. For the first time, it felt like they’re really on the path to achieving upper stage reuse. That was always the biggest “reach” of the entire program in my view, and today they took a major step forward.
Is it disappointing that they had a couple of engine outs, and also trouble with the booster relight? Sure. Do I have even a little doubt by now that they can fix these problems? None whatsoever.
I’ve been told by someone who was in the service that when smoking was no longer allowed on submarines, it made a huge difference in the cleanliness of machinery and thus how much work was required to maintain it.
Yeah, I’d love some of that goodness in my lungs, please.
When I encounter new terms, I look them up. Just like any other new word. Been doing it since I was a kid with a dictionary. Now, it’s too easy not to. There is literally no excuse.
Not sure why this is being downvoted, but it’s absolutely correct. For most of the history of computing, people were happy that it worked at all. Being concerned about energy efficiency is a recent byproduct of mobile devices and, even more recently, giant amounts of compute adding up to gigawatts.
This take is anachronistic. Thermal issues were evident by the late 1990's. Of course by that time not many were working in x86 assembly but embedded systems sure cared about power.
People forget embedded predated mobile by a good 20 years.
If you can remove 17% of your code, or even just avoid building it, yeah you probably should. That can be a really rough tradeoff though. (And the sibling comment is also right that deleting 17% of code != 17% faster builds, though I could see it being higher or lower)
My friends and I have been deriving much amusement from the comms issues. We can fly people around the moon, talk with them, send back high res video, but talk to the boat that’s close enough to swim to? Forget about it!
reply