ud_0

Maybe, IF the hatch can be opened when there is a pressure difference. It might be dangerous or even mechanically locked out in those cases. It may not, I have no idea.

I mean we're just guessing and spitballing here, and all of this assumes that whatever incapacitated the CMP is fixable by the other astronaut. But it does look like there may be a decent chance the CMP could survive this. Of course, he might have internal injuries or they might not be able to restart his heart. But seems like this procedure would be worth a try.

> - Help incapacitated astronaut into suit (temporarily removing own suit if necessary) > - Once both suited up, open airlock again to admit remaining astronaut

These steps don't seem to be necessary. Since the CM can be opened from the inside towards the LM, the third astronaut could just wait in the LM and be let in that way.

I think the only question is really how quickly can you repressurize the CM.

It was basically a cone-shaped pressure vessel 3.23m tall and 3.91m wide, that's 51.71m^3 of volume. I'd estimate about 50% is taken up by machinery, so how fast can you repressurize 25m^3 to 1/3 sea level (which was apparently standard for the spacecraft)?

My guess would be it could be done pretty quickly, maybe 2 minutes?

With recent content, I prefer to know how many hours/days ago it was posted. I find that exponentially more helpful than guessing timezones and things like that.

However, you're completely right when it comes to timestamps exceeding a certain age. That's why in my own projects I use a mixed approach: display recently changed things in relative time and all others in absolute terms.

I also advocate to display more detailed information when the user mouses over a timestamp, just so the data is there if needed - as it is in this case.

Based on this behavior, my paranoid side is expecting a wave of copyright notices and invoices being sent to every single site that is using Unsplash images right now.

Repairability is guaranteed to be impossible if you have that level of integration, and I suspect that is a big part of the motivation behind adopting this.

I switched to Linux/Gnome from macOS about 3 years ago. From my perspective, they're both frustrating in different ways, but I would be okay using either one. Gnome is too simplistic and opinionated, KDE is too heavy and fragile (but I also don't have a lot of experience with it).

Overall, Desktop Linux works well enough for me to live with it. A few years earlier, that was not an option if you wanted to live a relatively normal computing life without missing out on too much or spending an inordinate amount of time on keeping your system alive.

I feel you, and I suspect that's a typical experience for someone with smarts, ambitions, and dreams but who never made it for one reason or other.

This is a feeling I know very well. This sinking feeling you get when nothing clicks into place and you struggle just to exist. Your peers' efforts often seem like glamorous rocketships taking off to great fanfare as they pass you by with ease. The self-inflicted pep talk about overcoming adversity and just sticking with it until you make it, when it's already plain to see for your friends and acquaintances that you're going nowhere. The truth is, this is normal. It may be your fault, it may be bad luck, you'll likely never know. The answer "try again, harder, try something different" seems trite and besides the point, but it's still the correct answer in my opinion. Life is an exploratory process for most people.

I think the question "why did I never..?" is the result of expectations that do not match normal human lives. Especially when comparing yourself to the likes of Elon Musk and Bill Gates, you need to realize that these are literally one-in-a-billion lives. While they may be especially gifted individuals, please do not discount the immensity of their luck and fortune.

Literally every single thing in their existence conspired to get them where they are today. When you read accounts or biographies of people like these, I invite you to pay special attention to casual references about what other celebrities they were connected to from an early age. All those weird "oh yeah, Neil Young usually dropped by our house every weekend for a jam session" moments.

However, I allege this is completely unconnected to being good at something. Being good at something is a product of effort and ability. Especially in technical and knowledge areas, there are very few gate keepers preventing you from getting good. There will probably be gatekeepers preventing you from practicing that skill, but then again, getting good is only ever the beginning of a journey.

I share your feeling that the author is throwing a lot of BS onto the wall, knowing that some of it will stick. I believe this is a well-executed tactic because I don't think this article is written for software developers, it's written for slacktivists and the public at large. There are just too many parts where he tries to hide behind generalized statements designed to garner superficial agreement.

The fact that this got a lot of exposure should serve as a warning sign though. The FSF is vulnerable and struggling to maintain relevance. Both the re-hiring and the controversy around RMS illustrate that in my opinion: whenever the discourse gets diverted away from Free software, it's a distraction they can ill afford.

Either they didn't know that this would happen or they wanted it to happen. In any case, they're now even more vulnerable to these kinds of hit pieces, and I'm afraid the RMS issue could generate enough public interest for larger publications to execute successful strikes against the idea of Free software itself.

Thank you for making a web version (don't have Android)!

I like it, but there is one usability aspect that I would spend more UI refinement on is the boundary between Wikipedia and the app.

For example, when I click on a related article, it opens that Wikipedia page in a frame, instead of opening it in Wikiyarn. I understand why, because you want to show detailed information. But that does prevent the most important function Wikiyarn could serve: guiding the user on a journey.

If you can still edit the title, I suggest prepending "Show HN".