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]).
The dog part is definitely key. We moved a few blocks — so within the same neighbourhood — shortly after getting our dog, and it was amazing how much more quickly we got to know our new neighbours with our (extremely extroverted) then-puppy compared to the previous place. (And, on the flip side, I'm on a first name basis with every dog on my block, which usually implies also being on a first name basis with at least one of their humans.)
I could also say the same, including the Wayland origin story. I'm pretty new to Niri — I only started playing with it about a month ago — but it's just absolutely that little bit more than Sway I didn't know I needed.
Completely agreed. My Rust origin story wasn't about memory safety, fearless concurrency, a modern type system, or anything else like that. Not that I didn't care about those things — I did — but none of them were what convinced me to start learning Rust.
What did convince me was being able to prototype things for the C project I was working on while having access to a standard library that included basic data structures, synchronisation primitives, and I/O handling in a way that used best practices from recent decades. Everything else was just a bonus that I got to learn and use as I went.
Truth be told, I wouldn't mind crowdfunding an alternate stdlib for C for that reason. Everyone has a wishlist of patterns discovered after K&R bestowed upon us System V, that mesh perfectly well with C's philosophy and very minimal environments, and make modern programming much easier when you're dealing with lots of dependencies. (e.g. bounded strings/small strings, arena allocation, error chaining/coalescing, etc..).
An old, old Internet protocol that was used to get information on a user, and could be used by users to post updates from their .plan files. Essentially plaintext social media for people with Internet connections in the 80s and (early-ish) 90s.
Reimplementing it (well, the CLI program, `finger`) also happens to be the final exercise of Haskell Programming from First Principles, after 1200 pages of glorious buildup from the lambda calculus forward, in case that sells anyone on trying it ;)
I had that "oh crap, I'm old" moment when my initial reaction was "what? You've never heard of finger?!" and then I remembered I last used it in the late 90s.
I'm glad your reaction was to assist the young folks. :)
