My partner (who isn't in tech, and isn't generally interested in tech) would probably literally stand in line for an updated version of the 12" MacBook on day one.
I was actually working on this last week, funnily enough. I've been working on a capability analysis tool for Rust, and if you're already generating a call graph via static analysis, taking that and matching it against the function-level vulnerability data that exists in RustSec isn't that hard.
ai was also one of the ccTLDs that had an MX record for a long time, and I believe (although never had reason to confirm) actually used it. foo@ai tended to be a fun test case for e-mail validation.
As a non-American, I think the thing I'm hung up on in what you said is that I don't understand why a developed country should allow anyone to be "uninsured".
Very pedantically, because PHP doesn't require copyright assignment, it would be (almost certainly) impossible to retroactively change the licence on older versions.
However, since the PHP and Zend licences both permit the user to use PHP under the terms of whatever licence version was applied to that PHP version or any later version, the point is essentially moot, since a user can choose to use the new version of the PHP/Zend licence once published, which will give them the same rights.
The standard supports a repository_url "qualifier" (query parameter)[0], which can be used to override whatever the default registry is (which, for Docker, is hub.docker.com[1]).
reply