• 1 Post
  • 37 Comments
Joined 5 months ago
cake
Cake day: January 23rd, 2024

help-circle


  • Cause no one wants to look like the idiot. And when no one has read the article, it’s a lot harder to dispute the claims of what the article is about. It’s a vicious cycle - someone who hasn’t read the actual article makes claims about it, others who also haven’t read it react and before you know it, you’re ten posts deep, arguing about something that may or may not have happened. All it takes is one person to make an under-informed post and another to pick up on it. The difference between thousands and millions of users affects only the probability of it happening.


  • They’re probably still poring over the data. Telemetry from the temperature sensors, the feeds from the internal cameras, data from the booster and why two of its engines failed and so on. Most likely also data on what and how many TPS tiles S29 lost on the way down, I doubt the video feeds were their only way of checking those All in all, it’s gotta be terabytes of data to sort through and analyze








  • Point 1: SpaceX’s entire development philosophy is “test early, test often and learn from failures”. This is a much quicker pace than simulating every imaginable failure scenario and leads to faster progress in development. With the Falcon 9, that process proved wildly efficient and successful, culminating in a launch vehicle so reliable that it’s cheaper to insure a payload on an F9 that already has multiple launches under its belt than a brand new booster. And they’re turning enough of a profit to develop the Starship largely on internal funds, seeing how the early Raptor flight tests were before the HLS contract.

    Point 2: Just adding, the Raptor engine is the first full-flow staged combustion engine to ever get off a testing stand and actually fly. The engineering complexity of these things is on the level of the Shuttle’s RS-25.

    Point 3: SpaceX were the only ones with more than designs and mockups to present, and they had a reliable track history from working with NASA on the commercial resupply and crew projects. And I see no problem with awarding a contract to a bid that actually fits into the budget.

    Point 4: Multiple options was always part of the plan. NASA wants redundancy, so that if one of the providers runs into problems, the other provider can continue (and perhaps even take up the slack) instead of everything coming to a grinding halt. For a perfect example, look at the Shuttle and Commercial Crew programs. The Shuttle got grounded and since it was NASA’s only manned launcher, they had to bum rides from the russians. In contrast, the CC contract was awarded to Boeing and SpaceX. With Starliner’s continued issues, SpaceX has picked up the slack and fulfilled more than their initial contract in launches, instead of NASA having to bum rides from the russians again. The initial HLS contract was supposed to go to two providers, until the budget got cut. Blue’s bid was always the favorite for the second pick.




  • No more pre-defined dialog trees for NPCs and more reactive interactions. An example from BG3:

    Tap for spoiler

    you can find evidence that Isobel, the cleric who keeps Last Light Inn safe from the Shadow Curse, is the resurrected daughter of that act’s boss.

    But you can’t talk to her, or anyone, about it, since those conversations were never written. With a system that generates NPC dialog on the fly, based on context and the NPC’s pre-defined parameters, you could.





  • Your issue, as far as I understood it, was that the brain implants are pointless, cause they do nothing we can’t already do. There’s plenty current medical technology can’t fix, but a brain implant could (one day). Such as restoring sight by bridging cameras to the visual cortex; or restoring control over their body to disabled people, either by bypassing damaged nerves anywhere in the body or connecting prosthetics to the motor cortex. Are those things worth the trouble of going through brain surgery?