You are not exactly wrong, just slightly. 10 000 kcal of bananas is about 10 kg.

10 000 kcal is 25 litres of Coke, or 5 kg of avocados, or 4 kg of Big Macs.

None of those amounts are reasonable to consume.

Wow, you are so wrong. The human body (and our microbial friends in our stomachs) are extremely good at digesting food. For any reasonable amount of food, KJ in = KJ stored + KJ expended.

It doesn't matter if it's fruit or Coke, you keep those calories. Plus, there is more energy in a banana than in the same weight of Coke.

No he's not, LEARN TO READ ffs.

He's saying that you shouldn't believe someone who says they are a truck. They are LYING to you, they are actually just a person in a truck outfit.

Wait, what?

> assuming that this might not have happened on the Moon

I can't find this quote anywhere in the summary or the story. Where did you get it?

One GREAT advantage it has over your bog-standards filesystems like NTFS and ext4 is its copy-on-write architecture, and the essentially free and near-instant snapshot system it provides.

When you take a snapshot of a filesystem, it simply makes a copy of the superblock. All of the space on the devices remain marked as in-use, and both snapshots share exactly the same physical storage.

When you make a change to one of the snapshots, it simply writes the changed blocks to a different location on the underlying devices and leaves the still-in-use original block alone.

This is completely correct. By having knowledge of all layers, ZFS is able to easily offer features that other systems don't.

One of my favourites what happens when you set a filesystem to keep two copies of a file. Instead of placing the second copy on a random device determined by the RAID layer, it will attempt to ensure that all blocks from one device are placed on the adjacent device.

The advantage of that is non-obvious at first glance, but what it means is this: When two devices in the JBOD fail, instead of corrupting all the files when *any* two devices fail, it means you will only have corruption when two *adjacent* drives fail.

In a 5-device JBOD, that means the chance of corruption when the second device fails drops from ~100% to 25%.

I run ZFS on any / every machine I can, server or not. That is one filesystem where the features outweigh all possible concerns.

http://www.aisb.org.uk/media/f...

I thought Lisa gave the best answers, expecially to the basic logic questions.

No grammar nerding needed, that sentence should annoy anyone with a basic understanding of English.

Indeed it was: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2F...

So with this API stuff, what you are proposing is that all systems should be divided up into functional blocks, where every block has a single logical purpose, and that savvy users are able to chain these functions together however they see fit to suit their purposes?

Where have I heard this idea before? Oh yeah... it's called The Unix Philosophy.

No, you are not.

Thalidomide work great for almost all users. The unborn fetuses of the users were what was affected.

Except of course in the many European places where they require KJ to be displayed instead.

Indeed. It does seem like she is more likely to favour people more like her (ie. competant in their profession or hard-working) over those who had their success via luck or inheritance.