Theoretically, in this case, the agonizing "It's pouring rain, blowing cold wind in your face, kids are screaming and hitting each other, you stubbed your toe into cart and generally just having bad day" scenario making any man unable to manage the extra-harrowing effort of directing a cart a few meters into a designated space.

> [..] I can't imagine how useless an unthinking AI would be at this when my own family and friends who, and this is important, _know me_, can't find anything to get me that doesn't land in the above categories

This is precisely the problem - an AI does not really "know" the recipient (set aside of what it means to "know" someone). The result is you get something just a bit more varied than the usual "He's a Guy - he'll love some Whiskey Stones, a Bacon-of-the-Month subscription, or a Beard Care Kit" advice. (Adjust for whatever target demographic.)

Acceleration by using the x86 AVX-512 extensions is especially compelling. Since ARM64 processors are becoming pervasive in server-side systems, is-there/will-there-be any optimization using the ARM64 NEON vector instructions in current or future Go versions? (The NEON instructions are 128-bit, instead of 512 bits in the AVX-512 set, but may still be useful.)

A former coworker who was a serious gun enthusiast experienced dangerously high levels of lead in his bloodstream - he had chronic headaches and other bodily pains. He visited shooting ranges several times per week, and also packed (assembled? made? I'm not sure the nomenclature) his own bullets. His doctors believe he aspirated atomized lead particulate doing so much shooting practice, and/or bullet manufacture. He underwent chelation therapy (a protocol involving taking certain medications that bind to heavy metals in the blood, and the patient excretes it out via urination) to reduce lead levels.

The risk would mostly be from the range, not the reloading. The problem is bullets are intended to scrape pretty hard against the barrel to get them spinning. That inevitably causes lead dust and indoor ranges can be pretty dangerous because of it.

I use command-line tooling much more than IDEs (e.g. VS Code), so the `gh` command-line tool (https://cli.github.com) for doing most of the usual hub-oriented workflow (PR authoring, viewing issues, status updates, etc) really helps a lot - I don't have to constantly <cmd>+<tab> to my browser, and point-click-point-click through web pages so much. It would be fantastic if ersc or any other jj-centered code-sharing hub had similar tooling early on.

I'm a big CLI for VCS person, so yeah, I use those tools too :)

There is a difference between "giving" and "taking".

There is! And my company has a legitimate interest in taking if the opportunity presents itself. We are a paper clip maximizing operation, not a charity

Back in the early '90s, I was a big fan of the C/C++ debugging library "electric fence" (written by Bruce Perens) - it was a malloc() implementation that used mmap() to set the pages of the returned buffer such that any writes in that region (and even read accesses!) caused a segfault to happen, and the program halts, so you can examine the stack. It was a godsend.

> there are many languages in popular use that can do this, in many cases better than golang

I'd love to see a list of these, with any references you can provide.

Erlang, Elixir, Ada, plenty of others. Erlang and Ada predate Go by several decades, too.

You wanted sources, here's the chapter on tasks and synchronization in the Ada LRM: http://www.ada-auth.org/standards/22rm/html/RM-9.html

For Erlang and Elixir, concurrent programming is pretty much their thing so grab any book or tutorial on them and you'll be introduced to how they handle it.

Haskell would be one of them. It features transactional memory, which frees the programmer from having to think about explicitly locking.

I don't understand why, if the recipient of the initial detached "hello" is annoyed at the communication tax of having to acknowledge it before the querier gets to the real point of the convo, why in the "preferred" example, he/she responds to their gratitude ("ta") with a "np"? That seems like just as much pointless communication noise, only at the other end of the chat. When I say thanks to anyone in real-life verbal communication, their (usually a grunt) "no problem" adds nothing.

It's mostly about flow, you are already interrupted by the hello, and may have to wait some time before their response to your reply (as they then have to type out their actual question.

Thanks/No problem is closing off the interruption so there's no future expectation.

It's not about trying to eliminate social interaction, it's about minimizing asynchronous overhead and unnecessary waiting.

That last "np" is a little nicety that lets the other person know their question was happily answered, no waiting created.

The J Peterman catalog is still around around (at least, online) and approaches satire in its selection of goods (mostly clothing) that assiduously conveys "casual, interesting, old-money wealth". The Elaine Benes character on "Seinfeld" worked there, and had to deal with the kooky habits of the Mr Peterman character.