I once had a user who refused to let us install a new version of our app on their machine, saying “I don’t want a new version, I want you to fix the version I have”.
A seasonal question: what candy that is available globally has the worst-tasting American version?
My vote is for KitKat.
Rules: this is for things that are supposed to be the same thing in the US and globally. This isn’t related to naming i.e. smarties in the US are a different thing to in the UK. Milky Way in the US should be compared to a Mars Bar. Also “kinda the same thing” doesn’t count i.e. you can’t say Malteasers/Whoppers they’re different (otherwise that would be the runaway winner).
Since people are still talking about Dune 2, here’s my contribution, which is that I was disappointed they left out 1/ the part about how Salusa Secundus and Arrakis were similarly harsh and 2/ basically anything about mentats
The boy wanted to know what a SCART cable looked like. I checked my box of emotional support cables and was sorry to discover it doesn’t contain one.
He said a picture would do but it really won’t. You have to hold one, to try twisting it and feel the resistance and hear the crinkling of the inner wires, to stare at the giant plug and poke its sharp connector teeth, to truly understand it.
In What's new in Swift I mention the performance improvements from the new Swift implementation of Foundation. Performance came up a lot when we first put the open source package live, but wasn't easy to talk about until the new OS betas were available.
One common trope at the time was “it isn't faster than using Objective-C, this is just to reduce Swift bridging costs” and while that's true, it's important to note Swift is just plain faster, as seen even when calling into it from ObjC.
There's this increasing tendency to talk about memory safety as if, because it's the most pressing problem right now, solving it means you've won the battle. But that's not the end goal… it's the start. Literally the least you can do.
Experimental support for generic noncopyable types in the #swift standard library is now available in the nightly toolchain.
Here's a simple demonstration of adoption of this feature on the Swift Playdate example project. Switching the Sprite type from an enum+class box to a simpler non-copyable struct drops binary size from 7k to 6k on the SwiftBreak game.