It is not a natural assumption that someone will digitize the artwork and use it to adjust a couple thousand matrix coefficients in a complex computer program. To most people that seems like copying with extra steps. The brain may in some ways resemble a computer, but what sets it apart is that we have always lived with brains. Everything a human does has already anticipated the presence of other brains, while etched circuits on ultrapure silicon crystals are something new.

None of the private equity chains with the sans-serif fonts, simplified logos and trisyllabic names are doing this, though. It's bad marketing. Patients don't want to walk outside to an MRI machine in the parking lot. It feels sketchy. Never mind that they score just as well on the ACR image quality tests as the in-room machines. Who the hell knows what that is?

In reality, it's the county hospitals and big universities that use them! Places that have in-house physicists who can argue for what really makes sense in practice. A major problem with healthcare as a business is that the customer does not usually understand the product, but they still need to buy it, and there are time constraints.

The sources you've linked discuss mostly the recovery of additional metals on top of what we have already recovered. That's a different and much harder problem. It's worth remembering that historically, the amount of metal obtained was much smaller — the vast majority of the copper that has ever been mined was mined in the last century, even though humans have been using copper for thousands of years. But historically, that copper was mostly used for consumer products, while today it becomes electrical cables, so it's less obvious how much copper we all use. There's surely enough copper in the walls of my apartment for everyone living here to cook in a copper pan, even though we think of copper pans as being too expensive nowadays.

The problem with modern architecture, in my opinion, is its preference for "dramatic effect": long contours, flat surfaces, high contrast. This is visually exhausting. It looks nice in a catalog and from a large distance, but it's uncomfortable to be close to. This doesn't follow from the use of more glass. It's a historical coincidence that the float glass process made windows cheaper around the same time that architects started experimenting with smoothness.

You're equating life skills to professional skills. I was not taught to milk a cow, but my milk comes from someone who was. The topic is whether software engineers in a professional context learned certain things about software.

Comments URL: https://news.ycombinator.com/item?id=49549174

Points: 3

# Comments: 1

When nuclear power became a thing in the seventies, there was massive planning around a presumed nuclear-powered future. The largest energy storage facilities in the US were all built around that time. This turned out to be a mirage as the cost of nuclear went up with the safety expectations of the electorate, while petrochemical prices dropped. But this time it's not prices we're predicting, it's temperature, which is much more reliable.

The other thing is that for a nuclear reactor, you need many kilograms of uranium. But for a Pluvicto patient, you need less than a gram of ytterbium.

Ultimately "make better rules" is only half the battle. You still need a process for implementation.

Including a rather unusual battle between the Tang Dynasty and the Abbasid Caliphate:

https://en.wikipedia.org/wiki/Battle_of_Talas

It's recorded that the Caliph, on hearing of the battle, said "What is this? A crossover episode?"

TextEdit on Mac uses RTF. Perhaps that's why Windows switched.

>[...]

>But remember: I’m not really building applications for other people to use. I’m building them for me.

Giant caveat to the whole argument and it's buried 80% of the way down. Granted, he alludes to that a little earlier, but if other people using your application are a completely irrelevant outcome, you're an unusual case.

I mean, sure, I make tiny one-offs, but those barely even have something you could call a CLI. I push as much complexity into command-line options and config files as possible.