Ink flow in a fountain pen is via capillary action (touch nib to paper, ink flows), as opposed to a ballpoint pen where you have to apply a small constant amount of downward force for the ball to have enough friction against the paper for the ball to roll. This might not seem like a big deal, but if you're writing a lot, it means that your wrist & hand will get much more fatigued with a ballpoint over time.

Put another way, ballpoints have absolute advantage over fountain pens, except for "sitting down and writing a lot."

UPDATE: Also, sir, this is an Arby's.

How many?

You pay: $20,000 in $some_coin (ignoring gas fees for the moment) 1/100 of annual royalties is $1,142, taxable at your marginal rate (say 20%), so $913 free-and-clear.

Even without doing discounted cash-flow magic, that gets you to an annual 4.5% annual rate of return. Not great, not terrible.

BUT, you're doing this all in NFT-land, which means either you hold it (in a cold wallet, ready to be shown once the next royalty agency asks who owns this stuff), some other entity holds it (and you trust them and pay their fees), and no one has stolen your metaphorical apes over the next 21 years, which is just what it would take to make back the investment. Also, making the double-bank-shot bet that courts will recognize NFTs as proof of ownership, and that the NFT itself does not become taxable property, as a security.

Short of some kind of presumably inherent joy in interacting with a smart contract, I'm really not sure what you intend to gain, here.

I'd love to be wrong, but I'm not seeing a good alternate explanation.

I'm 100% on board with trying out a new terminal that is fast and has features, but there's an implicit expectation of the simplicity of the communication channel, and... this is not it.

Density of ice at 0 degC is 0.92 kg/L. So, 1 kg of ice =~ 1087 cubic centimeters of space, or a cube ~4.25 inches on a side.

Rounding that down to 4 inches for the moment, you get 27 of those per cubic foot, or (260 Wh * 27) = 7.02 kWh, and then round that down to give the extra quarter-inch back, you get ~6.5 kWh/ft3 theoretical capacity.

A typical household in the US uses 10,715 kWh/year[0], so (10715/6.5) = 1648.46 ft3 for a household's worth of freeze-thaw battery storage, or a cube 11.81 feet on a side.

Yes, of course it's more complicated than that, but the scale is pretty interesting.

---

[0] https://www.eia.gov/tools/faqs/faq.php?id=97&t=3

That is, an empty seat has value until the plane takes off, at which point the value goes to zero. On the flip side, a traveler has an opportunity to be in that seat until the plane takes off, at which point its value is zero. People tend to understand that those values continuously vary with time, and so the price will vary with time.

To contrast, books (in specific) and consumer durables (in general) are not perishable goods. The notable exceptions tend to be time-based; try getting chocolates in the heart-shaped box right before Valentine's Day in the US... and then the day after. Since the value of the book doesn't continuously vary with time over the short-run, people don't expect that the price will vary.

Yours?

That is, "I have this seldomly-updated list of ~10000 things, and I'm going to need to join it against my time-series data."

With other time-series databases I've dealt with, it's an afterthought at best and the answer is typically "Enrich the data via flink/benthos/etc. on import and avoid using any kind of join."

Does Timescale's use of PostgreSQL circumvent this issue, both in terms of storage of lookup tables, and performance on join?

https://en.wikipedia.org/wiki/Leonard_P._Zakim_Bunker_Hill_M...