And the collision of the RMS Olympic (the first of the three in that family) with the HMS Hawke. As did the coal stoker Arthur Priest

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

That is correct, if the first few records (a virtual block size sorta) (not sure how many off the top of my head) don't compress well, it assumes that the file is not compressible and just writes the data out skipping the compression step.

That quote doesn't contradict what mkl said, towards the end of the article it does say this thou, "The cloak will be on display in the new museum developed in Perth, set to open in Spring 2024."

That clip never gets old, Sirocco (the birds name) sure has some attitude.

Well most of the politicians don't have a clue that any of that stuff is possible either.

3 attempts to get a hit for me, in NZ

Can hot-code reloading coexist well with inlined functions?

It isn't required (in the strict sense) to keep the dedup table in memory, the problem is that performance is dire when it doesn't. It would be pretty similar to virtual memory thrashing, when the table is not fully in memory.

Solid plastic might, but would moving water and impacts result in the bricks separating?

What happened to Germany (territory shrinkage and economic sanctions) after WW1 incidentally shows this story pretty well.