Earlier quoted context omitted.
The engine reuse isn't exactly the Shuttle program's brightest moment anyway. The SSME was designed for 55 uses… By the time of the Challenger disaster, that number was 4-5. By the end of the Shuttle program NASA counted themselves lucky when some of the engines managed 15 uses; and refurbishment between each flight was only marginally cheaper than building new expendable engines for every flight. Even with the added…
You're right, reuse didn't work out with the Shuttle nearly the way they wanted it to. But it did work out to some degree, while Buran's version of it never went beyond paper.
Space Shuttle vs. Buran
41–49 of 49 posts
Re: Space Shuttle vs. Buran
#42Obligatory shuttle reading: http://idlewords.com/2005/08/a_rocket_to_nowhere.htm
Ha! "You know you're in trouble when the Russians are adding safety features to your design."
Re: Space Shuttle vs. Buran
#43Earlier quoted context omitted.
You're right, reuse didn't work out with the Shuttle nearly the way they wanted it to. But it did work out to some degree, while Buran's version of it never went beyond paper.
But also because they pulled the plug on the Buran program because they had no use for it. They could shoot people up in rockets and that worked out cheaper for them. The Soyuz is the most cost efficient way to shoot people into space.
The Soyuz has been the most efficient way to shoot people into space since 1968. It was developed in parallel with Apollo, and instead of throwing it away after the end of the moon program, they just kept it, and kept improving it – had NASA kept Apollo and improved it instead of throwing it away, and then throwing its successor away, then cancelling two successors in a row, to spawn a grand total of four parallel programs to maybe find one successor, who knows where the US space program would be now.
NASA's problems are less technical issues, and more a management one.
Re: Space Shuttle vs. Buran
#44Earlier quoted context omitted.
Jesus Christ, 4MB? Did they write the whole thing in machine code?
Back in the day, not everything needed jquery and bootstrap deps to be considered "modern" ;) Jokes aside, russian space program had some AMAZING developers working in some very low-level languages with unbelievable efficiency. I had the pleasure of working with some of them many years later on enterprise software at large banks. NASA has written some amazing software as well. Start here: https://news.ycombinator.com…
Re: Space Shuttle vs. Buran
#45Earlier quoted context omitted.
Back in the day, not everything needed jquery and bootstrap deps to be considered "modern" ;) Jokes aside, russian space program had some AMAZING developers working in some very low-level languages with unbelievable efficiency. I had the pleasure of working with some of them many years later on enterprise software at large banks. NASA has written some amazing software as well. Start here: https://news.ycombinator.com…
You may joke, but Node.js is still going strong after six years, while Buran never went past test flights. Imagine how much farther Buran could have gotten if they had the ability to share small, focused, reusable modules with the community. Imagine how much more reliable their systems could have been, if they had been able to reason about them at a higher level of abstraction, without getting bogged down into the lo…
Also, check this out: http://www.fastcompany.com/28121/they-write-right-stuff
Very different from how a typical Node.js left pad module is implemented.
Re: Space Shuttle vs. Buran
#46Earlier quoted context omitted.
A large number of those missions were flow for the DoD, repairing/refuling satellites and potentially also capturing enemy satellites.
Large? Of the 135 flights, almost 50 went to Mir/ISS, doing work that should have been done by Soyuz/Progress/TKS-equivalent spacecraft in the $100-200 million range. 32 more made Spacelab flights, aka "poor man's excuse for a space station". The remainder were split between commercial satellite deployments (best left to unmanned boosters), regular scientific missions (the same already done on Gemini and Apollo capsu…
They obviously didn't use Shuttle exclusively for military purposes. But most people don't realize that nearly all government-funded scientific programs in the US also have significant defense/NRO objectives. Even The Dish at Stanford was funded to be used for SIGINT work during the Cold War.
I'd wager that these groups are now using advanced robotics to replace classified work previously done via Shuttle missions. i.e. Boeing X-37
I don't think there's any maintenance plan for JWSP, capsule or otherwise. L2 is way too far away. Do you mean maintenance after launch but before deployment?
Re: Space Shuttle vs. Buran
#47Earlier quoted context omitted.
Back in the day, not everything needed jquery and bootstrap deps to be considered "modern" ;) Jokes aside, russian space program had some AMAZING developers working in some very low-level languages with unbelievable efficiency. I had the pleasure of working with some of them many years later on enterprise software at large banks. NASA has written some amazing software as well. Start here: https://news.ycombinator.com…
You may joke, but Node.js is still going strong after six years, while Buran never went past test flights. Imagine how much farther Buran could have gotten if they had the ability to share small, focused, reusable modules with the community. Imagine how much more reliable their systems could have been, if they had been able to reason about them at a higher level of abstraction, without getting bogged down into the lo…
There's a reason RTOSs don't have very tall software stacks with multiple layers and virtual machines between them and the hardware.
When your garbage collector invoking at the wrong millisecond 0.01% of the time means everyone on the craft is incinerated in the atmosphere... that's a different level of reliability requirement.
Re: Space Shuttle vs. Buran
#48Earlier quoted context omitted.
You may joke, but Node.js is still going strong after six years, while Buran never went past test flights. Imagine how much farther Buran could have gotten if they had the ability to share small, focused, reusable modules with the community. Imagine how much more reliable their systems could have been, if they had been able to reason about them at a higher level of abstraction, without getting bogged down into the lo…
I get your meaning, but additional abstraction layers are equally dangerous because they obsfucate underlying constraints and result in incorrect reasoning about a system. There's a reason RTOSs don't have very tall software stacks with multiple layers and virtual machines between them and the hardware. When your garbage collector invoking at the wrong millisecond 0.01% of the time means everyone on the craft is inci…
Re: Space Shuttle vs. Buran
#49The principal functional difference between the Shuttles and Buran is buried in the last paragraph: The main advantage of Buran over STS is that it was made from start to be fully automated. The entire test flight from launch to the landing was done _completely_ autonomously. The most impressive part of it though was the landing when Buran aborted first landing run that happened to be into a strong crosswind and retr…
[1] https://www.quora.com/How-did-game-developers-pack-entire-ga...