The boat in the old photo (from 1928, apparently) is casting a pretty good wake, and the man aboard is holding a tiller attached to a rudder. It’s impossible to tell for certain with the low-res image, but entirely likely that one of those shapes in the boat ahead of him is an inboard engine.

It could be highly inconvenient, since the Isle of Mann and Isla Mujeres are so far apart.

Tell me it’s 68f out and I will fight you.

Note to self: High heat levels make Canadians cranky.

Around here, 32°F is very cold in October, but an occasion to wear shorts in February. (Both are still cookout temperatures, though.)

No, that’s not it, we’re measuring in incredulity units, which are syllables.

“One hun-dred and se-ven?!” == 6 syllables

“For-ty one?!” == 3 syllables

Also, the first one has more vowel sounds to really draw out to indicate higher levels of I-can’t-even. It sounds only golly-jeepers in Celsius, and much more I’m-so-done-with-this-shit in Fahrenheit.

Case-sensitive is easier to implement; it’s just a string of bytes. Case-insensitive requires a lot of code to get right, since it has to interpret symbols that make sense to humans. So, something over wondered about:

That’s not hard for ASCII, but what about Unicode? Is the precomposed ç treated the same lexically and by the API as Latin capital letter c + combining cedilla? Does the OS normalize all of one form to the other? Is ß the same as SS? What about alternate glyphs, like half width or full width forms? Is it i18n-sensitive, so that, say, E and É are treated the same in French localization? Are Katakana and Hiragana characters equivalent?

I dunno, as a long-time Unix and Linux user, I haven’t tried these things, but it seems odd to me to build a set of character equivalences into the filesystem code, unless you’re going to do do all of them. (But then, they’re idiosyncratic and may conflict between languages, like how ö is its letter in the Swedish alphabet.)