I actually think that you could craft good arguments for allowing trojans. It's the stuff in temporary resonance orbits that I was really thinking of. There are a lot of orbits that are only semi-stable, say stable for a century or two, but not for millennia.

Don't be hypnotized by the names. What is most significant (after the orbit) is the mass. And that's a pretty smooth gradation (at least on a logarithmic scale).

If you want "planet" to mean "stuff in orbit around the sun", you end up with most planets weighing micrograms...or possibly less.

N.B.: By the strict definition of "planet" used by the IAU, even Jupiter wouldn't really qualify, because it hasn't cleared it's orbit. There's a lot of small stuff and, of course, the trojans.

Yeah, but...
The guess at the size is based on the guess of the albedo. If it's covered with something dark, it a LOT larger. (I'm presuming they're guessing it's covered with methane ice.)

Plausible. Most communicable diseases are addressable by social habits...if you can get people to do them.

I disagree. I think it probably CAN get much faster, but I'm not sure how much cheaper it can get.

The approach I think could succeed is the "bio-chip", with lots of cells and feed lines so different wells in the chip would host different combinations of bacteriophage and sample. This would need to be screened frequently, probably by an AI, that would pick out the most successful set. I think this could, in principle, usually be done within a couple of days in a mostly automated way. But that's a pretty complex setup, and I doubt that it could be done really cheaply.

It's not even that. Most of the drug-resistant bacteria existed before antibiotics came out of the lab. But they weren't a very successful part of the population. Antibiotics killed off their competition, and now they're successful. Most methods of resisting antibiotics have an energy cost, so bacteria that don't use them are more successful if the antibiotics aren't around. Unfortunately, it's not usually a very high cost, so stopping the use of an antibiotic doesn't reset the population, at least not quickly.

But, yeah, bacteria mutate really rapidly to fill a new niche, so you probably literally CAN'T have an antibiotic both in wide use and remaining effective.

Actually, getting the CO2 out of the atmosphere is possible, but *quite* expensive. Thermodynamics + entropy mean it will take more energy to get the CO2 re-concentrated than it released in being created.

Not fair. There are applications for which nuclear appears to be the best solution.

But, yeah, solar and wind scale a lot faster and more cheaply, even when you include the needed storage.

Only in the most utterly pedantic sense of the word "different" wherein you mean that by definition, infant mortality occurs early and wear occurs later. But they can both stem from the same root cause, which is a component not built with adequate tolerances. In other words, they can be the same fundamental issue, just expressing themselves at different times.

Most products don't have an MTBF. And things that do have MTBF are based on accelerated wear testing on a small number of units, and can have almost zero basis in reality. There was one model of major brand hard drive about twenty years back where a couple of RAIDs where I used to work got lost because the drives all died after such a predictable number of powered-on hours that by the time you could re-stripe the RAID, the next drive would die. They ended up making sure the drives had a high variance in powered-on hours before using them in RAIDs after that.

It's an example that proves or demonstrates a point. And the point it was proving was that the same root cause can be responsible for both catastrophic early product failures and premature deterioration-related failures.

If you're invested in the company, you have a reasonable argument. If you're hoping for a job, you don't. (But see the comment by TWX.)

Wear-out failures aren't always different from infant mortality failures, though. If the defect is caused by a design flaw in a component resulting in a structural weak point, that same weak point could fail after one use or a thousand, and it could just be a ticking time bomb. Someone could get very unlucky and find one that is slightly weaker, and it could break much sooner.

Case in point, I recall a machine where some people would have to have their laptops replaced every couple of months for motherboard failures, while others lasted for years, and it turned out to be dependent on how people closed their laptops at the end of the day and whether they pressed on the bottom of the case in a particular spot that wiggled the GPU. But if you handed one that had been working for five years to someone who used their left hand under the laptop while closing it, it would be dead in two or three months. If you replaced it with a brand new one, the brand new one would be dead in two or three months. And so on.

You left out that he doesn't only have one class.

Well, the use of AI *should* be encouraged, but that's a lousy way to do it. After graduation the students will need to live in a world where they deal with AI...but we don't know what the shape of that world will be.

OTOH, the main thing you're supposed to learn in mathematics classes is "the shape of mathematics". Learning to do the mathematics is secondary, now that calculators have advanced to AIs. (I've become nearly dependent on spell-check, but I don't really think of this as a problem.)

The tapes I was talking about were 800 bpi reels even parity. (The odd parity ones had better error recovery.)

That would have been really useful for some mag tape systems I used to use. They had too many errors for their error correction system.

OTOH, this kind of thing is very likely to have bugs. Test it THOROUGLY before folks start depending on it. Perhaps, after it passes initial tests, make it an optional choice in the installer, and require extra steps to do the install (with warnings: CAUTION: BETA FILE SYSTEM HAS BEEN CHOSEN).

File systems need more thorough testing that most software choices.