Hacker Newsnew | past | comments | ask | show | jobs | submit | amykhar's commentslogin


Fingers crossed that this https://idlewords.com/2026/03/artemis_ii_is_not_safe_to_fly.... doesn't have any effect.

Of course it's not "safe"! We put a ton of explosives into a huge can, put a small can with humans on top of it, set it on fire and try to control what happens and get the humans into space, and then we try to drop the same can from the space, while it's traveling at miles per second, and land it on the ground. It's not "safe" and won't likely be "safe" in our lifetimes, there's always big risk, that's why astronauts get so much respect - they take a lot of risks. These risks become smaller with time, but still they are quite serious. And of course anything that reduces risks - while not disabling the whole program - is good, but I don't think "safe" is the word that is justified when talking about those things.

What he means and you're interpreting a bit too literally is that this [heatshield] is one subsystem where the risks are not well understood or quantified as, say, the propulsion system, for which we have a lot more experience and flight heritage.

Yes, of course there are risky systems in there, and calling attention to one of them is fine. What I object to is framing it as a "safe/not safe" issue - as if without the tests the author proposed it were "not safe" and with them, by implication, it would become "safe". That's not like replacing old tires on your car with new tires - there are a lot of things that can go wrong, and many of them are "unsafe", and it's always a complex equation which can not be (at least at current level of technology) solved with doing more tests or anything else to make it "safe". The "safe" framing is the one I object to.

Recent and related:

Artemis II is not safe to fly - https://news.ycombinator.com/item?id=47582043 - March 2026 (598 comments)


There is a LOC (Loss of Crew) number that is typically calculated for these missions. I'm curious what that is? Early Apollo missions were on the order of 4%.

Before the Apollo launch, von Braun was asked what the reliability of the rocket was. He asked 6 of his lieutenants if it was ready to fly. Each replied "nein". Von Braun reported that it had six nines of reliability.

I'm assuming this is fake but it's hilarious.

GitHub taking notes

Is that a real fact?

(I misremembered it slightly, so sue me)

From "Apollo The Race to the Moon" pg 102:

The joke that made the rounds of NASA was that the Saturn V had a reliability rating of .9999. In the story, a group from headquarters goes down to Marshall and asks Wernher von Braun how reliable the Saturn is going to be. Von Braun turns to four of his lieutenants and asks, "Is there any reason why it won't work?" to which they answer: "Nein." "Nein." "Nein." "Nein." Von Braun then says to the men from headquarters, "Gentlemen, I have a reliability of four nines."


Reliability of 4 neins to be precise

You know why you chose 6 9s.

The date checks

After the moon landing, Armstrong allowed that he had estimated the survivability at 50%.

In 2014 an independent safety panel estimated 1:75, but I think it's slightly better now. The shuttle program officially had a limit of 1:90 but in practice achieved 1:67.

In the early days of the Shuttle program, the probability was supposedly estimated as low as 1:100,000. Challenger brought on a more realistic approach.

The official minimum standard is 1:270

Hilarious!

He wasn't really getting rid of stuff though. He was moving it to "cold storage" so the primary storage was clear. When he needed a rarely used thing again, he could get it out of cold storage.

When I was growing up, I remember some drama because East German and Soviet male athletes were trying to compete as women. If male to female trans athletes were allowed to compete, I imagine it would just be a matter of time before a female athlete would HAVE to be trans in order to stand a competitive chance.

your imagination is wrong. obviously.

Doubtful. Despite your articulate counter-argument, I am unconvinced of your viewpoint.

This is interesting. It seems like it may only be applicable to brand new projects though. Could you envision it working for large, existing applications that wouldn't have specs for the existing code?


No reason it can't. I know people currently generating specs from existing code; just gotta write the pipeline.


Businesses should definitely support the open source projects that they use. I'm still astounded that professional developers seem so adverse to paying for the tools and libraries that they use to make their own money.


I'm frankly disappointed that number isn't much higher.


I watched that video the other day and immediately ordered an Instant Pot


Cause what this country needs is to automate away even the gig economy jobs that are out there. Let's keep making a few people rich and screw all the normal people out there.


Why the downvotes? That jobs will be lost is fact. Does this represent an increase in wealth concentration? Obviously. Is that a net bad? I don't know, let's discuss instead of silencing people.


I also hated that they were trying to make it a free tool, which would mean selling user data to make money, and would require growth at all costs.

These days, I'm trying to migrate to paid tools. I would much rather work with a slower growing company that has a real business model other than grow and sell out.


Same. Old business models make more sense to me and seem healthier for customers, employees, and the economy. Growth at all costs, with the goal of a quick and profitable exit only benefits the founders, and is generally a net loss for society as a whole.

I can’t say I’d be above taking the briefcase full of money when dangled in front of my face, but when that’s the goal from the outset, the incentive structure feels backward.


> a real business model other than grow and sell out.

This is why I have problems trusting any new SaaS these days. The industry has changed from wanting to build a good product to wanting to grow fast and then exit, and typically the users get screwed.

You just can't trust that anything will stick around, so why bother adopting the tool in the first place, especially for anything that's not open source.


Assuming the business has access to the data, the backup plan for the business is always to sell the data. There is very little chance the leaders of a business simply wind down the business and close the doors.


I share your sentiment but still can’t imagine adding a browser-specific AI subscription alongside my current GPT or Claude sub.


I don't really need AI in my browser. I do like spaces in Arc, and how it handles cleaning up my tabs. The color coding of the sidebar for the various profiles is the one feature I haven't been able to find in things like Orion, Vivaldi, Firefox, etc. By color coding, I mean the ability to make the entire sidebar a different color, which helps me make certain I don't do stupid things in prod.


Agreed; the occasional Raycast AI query using their web extension suits me well.

Haven’t used Arc as my daily driver in a while now, but I used a similar setup with a semi-bright green sidebar as my debugging space when my last project was in active development. I’m rarely at a desk these days so back to Safari for the time being, but one thing I miss the most is Arc’s near-borderless window ‘frame’.


Dia was paid. Dia Pro cost $20/mo


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: