Comment by teachrdan

Comment by teachrdan

I'm going to keep this conversation going because it's interesting to me, if no one else here.

As to reaching 800+ Celsius: This is a solved problem on Earth because we have an effectively unlimited supply of oxygen and fuel. Neither of these conditions is true on Mars, unless you count the (very toxic to humans!) perchlorate in the soil. Extracting potable water from Martian soil would be a non-trivial task just in terms of energy needs, much less the task of making the water safe to drink.

The radiation issue is a bigger deal than you let on. I did not know about Ramsar. It's interesting! But this is a town of only 2000 with people who may have adapted to its higher levels of background radiation over generations. Our hypothetical Mars colonists will not have that luxury. And Ramsar has, on average, "only" 10x more radiation than we have on Earth -- still only 1/5th what we'd have on the surface of Mars.

I'd also point out that you seem pretty blase about the long-term risks of radiation. If we're talking about real colonization, we have to consider the risks of literal, multiple lifetimes of radiation -- not just how it might affect an average person over the course of a few years or decades.

> The idea of trying to just work out everything at home, and then have everything go perfectly is what I would call the meme

I apologize if it seems like I'm saying we need everything worked out. That is a miscommunication on my part. But we need some working prototype of what could work -- which we don't. We've never even succeeded in building a self-sustaining closed system on Earth! Where it should be easy! Because it's actually really really hard! And the craziest part is, literally no one is even trying!

If we can't make a self-sustaining closed system work here there is no reason to believe we could do it on another planet. I know SpaceX is everyone's favorite model of "go fast and break stuff", but there's many reasons why that does not apply to space colonization. The obvious first reason is that blowing up a rocket is not as serious as accidentally killing a space colony.

Another is the (imo mistaken) belief that rocked design is analogous to space colonization. I'd hazard that space colonization is maybe 1000x more difficult than designing a real big rocket -- which is admittedly very hard! But there are a bunch of extremely important and difficult questions that advocates for space travel -- maybe even you -- seem totally uninterested in solving and hand-wave away.

Resources will be scarce on a space colony, at least for the foreseeable future. What if a baby is born with a pathology that makes their care too expensive? Will they be left to die? Or will they have a right to live indefinitely? Will their parents be forced to get sterilized -- or have future fetuses aborted -- if they are at risk of producing more children with the same pathology? Who decides who gets sent home? It's simple if someone has an extreme psychic break with reality. But what if it's someone with severe depression? Or borderline personality disorder? Will the colony get to vote people off the island like the ancient Greeks sent people into exile? And what if a trip home might kill the person in question -- a particular risk for people who are born on Mars and never experienced gravity on Earth? Do future colonists have the right to give people an effective death sentence for being mentally ill?

These are obviously problems that exists here on Earth! But the consequences are entirely less dire here. A person with severe schizophrenia can live on the streets here in the US and pretty much no one gives a shit. But if this happens on Mars, and that person is using resources that are already in short supply (think of a world where there's only enough water to shower for a few minutes a week, or to subsist on only a bare minimum number of calories), people are going to care a lot. What happens next?

Replies teachrdan · 2026-09-17
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.