A memory safe language is one for which (a) there is a subset of programs which can be statically proven to not perform unsafe memory operations at runtime and (b) no programs outside of this subset will be accepted. The set of operations that are considered to be unsafe can vary, but always includes writes to unowned memory, and often includes reads from unowned and/or uninitialized memory.

Tesla confirms it has given up on its Cybertruck range extender

> would it truly be an Apple mouse if it didn't have at least one questionable design decision?

I don’t know if you consider a single button a questionable decision, but the ADB II mouse was as close to perfect as the technology was able to support when it was released.

I make a habit of asking support whether things I’m buying are commingled. First-level support used to be able to tell me pretty quickly (and I got both “yes” and “no” answers), but these days I’ve had to escalate most of the time. Kind of nuts to me that it’s worth ten minutes of support time and twenty minutes of supervisor time for them to sell me a $3 usb cable, but they’re the ones paying, so…

Still quite common in NYC. There’s a bit of a social distinction between doorman buildings and elevator-man buildings, and some people prefer the latter.