• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • The only fuel you can make from water is hydrogen. The RS-25 engines used on the SLS core stage and the Space Shuttle used liquid hydrogen, as did the J-2 engines on the second and third stage of the Saturn V (but not the first stage, which used RP-1 (kerosene) burning F-1 engine)

    Starship’s Raptor engines use liquid methane however. There are a bunch of tradeoffs between the different fuels, but generally liquid hydrogen is more difficult and expensive to deal with. With low cost reusability being one of the primary objectives of Starship, liquid methane was chosen as the best option. The fact that it can also be manufactured on Mars was also considered, since CO2 is abundant in Martian atmosphere.









  • What is your source for this ? Recent polls show reunification support is still <2%, with about 6% open to reunification eventually but not now.

    In 2018, before the crackdown in HK, the reunification support was 3%, with 13% open to it eventually - the events in HK have definitely significantly eroded support for reunification in Taiwan.

    I have family in Taiwan and literally don’t know a single Taiwanese person that wants reunification with the PRC.


  • Early computers had very limited resources, RAM, storage, etc. (first computer I worked with only had 4k of RAM for example) It often made sense to only use the last 2 digits of the year as an optimization in many common tasks that computers were used for, as both the 1800s and the 2000s were far enough away that most basic date calculations worked fine. Also, the industry was changing rapidly, and few people expected their software to be used for more than a few years - certainly not for decades, so focus was usually on solving the immediate tasks as efficiently as possible, without much consideration for the distant future.

    However, it turned out that a lot of the code written in this period (70s and 80s) became “legacy code” that companies started relying on for far longer than was expected, to the point that old retired COBOL programmers were being hired for big $$ in late 90s to come and fix Y2K issues in code written decades ago. Many large systems had some critical ancient mainframe code somewhere along the dependency chains. On top of that, even stuff that was meant to handle Y2K was not always tested well, and all kinds of unexpected dependencies crept up where a small bug here, or some forgotten non-compliant library there could wreak havoc once date rolled over into the 2000s.

    A lot of the Y2K work was testing all the systems and finding all the places such bugs were hiding.