Obsolete/dialiectical English: to shudder with fear, or a shudder (related to "gruesome")

Computer games: in Zork, a monster that eats adventurers in the dark [0]

Linguistics: an English translation for words that cover the entire green-blue part of the spectrum (in languages that don't distinguish blue from green) [1]

Philosophy: a color name that is equivalent to green until a specific future time, at which point it becomes equivalent to blue (used to raise questions about how to validly extrapolate into the future) [2]

[0]: https://zork.fandom.com/wiki/Grue

[1]: https://en.wikipedia.org/wiki/Blue–green_distinction_in_lang...

[2]: https://en.wikipedia.org/wiki/New_riddle_of_induction#Grue_a...

That's basically what happened with the neutrino. Neutrinos were originally proposed in 1930 by Wolfgang Pauli to solve apparent violations of energy and momentum conservation in beta decay. He suggested that the missing energy and momentum were being carried off by some additional -- undetected and mostly undetectable -- particle. For a while, it looked like these proposed ghost particles might never be detectable, but Fred Reines finally managed it... in 1956, 26 years later.

So don't write off unicorn particles. Sometimes they're real, even if you have trouble detecting them.

[1] https://sandwalk.blogspot.com/2022/08/junk-dna-vs-noncoding-...

[2] https://en.wikipedia.org/wiki/Junk_DNA#History

[3] https://judgestarling.tumblr.com/post/154553548091/long-nonc...

(BTW, you never get a two-line pattern in a decent setup. This is an incredibly common mistake, but it's simply wrong. The interference (which produces fringes) only happens where the separate patterns from the two slits overlap, so if you want a lot of interference, you need them to overlap a lot. So in the no-interference case, you won't get two separate lines with a gap between, you'll get a single merged wash (with probably some fine structure due to diffraction within each of the slits, but that'll also be there when there is interference, on top of the two-slit interference fringes).)

You might think "ok, I'll do this with a bunch of photons, measure/not measure all of their twins, and see if the bunch of them show fringes." This is more-or-less what's done in the delayed-choice quantum eraser experiment, but it doesn't work out in a way that allows communication. What happens is that you always get the no-interference pattern. In order to see interference fringes, you need to split the individual photons' dots up based on the result of the measurement you made on their twins. Based on those measurements (if you made them), you can split the photons up into two groups, which'll have fringes with equal-and-opposite patterns (i.e. each will have bands where the other has gaps [2]).

If you didn't measure the twin photons (or made some other measurement on them instead), you can't split them up, so you won't see the fringes. But that's not because the measurements were different, it's just that you can't split them up afterward to see the fringes. And even if you did measure the twins, you can't split them up until you get a list of which twin got which result -- which can't be sent faster-than-light.

Net result: no, you can't send information via entanglement, you can only get correlation.

[1] https://www.researchgate.net/figure/Electron-Fringe-Pattern-...

[2] https://algassert.com/quantum/2016/01/07/Delayed-Choice-Quan...

But as far as I can see, using a close-bracket as the first character in a command is safe, since it cannot be treated as part of such a pattern. Open-bracket (without a matching close-bracket) would work in many shells, but will get you a "bad pattern" error in zsh.

Someone (I don't remember who did what here) discovered that they could get `SHOW SYSTEM` (roughly analogous to unix `ps` command) to display their name in reverse video by adding escape sequences to their process name. So a bunch of us started experimenting to see what else we could embed in there.

Most of the terminals attached to the VAX were Zenith Z-19s, which mostly emulated DEC VT-52s but with some added features. One of those added features was an enablable 25th line (in addition to the regular 24x80 display) that functioned as a sort of status line. We found we could enable that, write something into it, then use the "transmit 25th line" escape sequence to send its contents back to the VAX. I remember having to work around limitations like it sending an escape sequence before the 25th line (which confused VMS), and I think it didn't send a carriage return at the end... or something like that.

I don't think we ever got it to do anything terribly interesting, but it was fun to play with. And then IIRC a VMS update blocked control characters in the `SHOW SYSTEM` listing.

A couple of caveats, though: Apple encourages using the same account for everything, and their interfaces try to autopilot you into that setup. You have to pay attention, and find & choose the "I'll set it up myself" options. Also, Apple uses email addresses as the name/identifier for Apple IDs, so to set up multiple IDs, you need multiple email addresses. iCloud includes an optional email account, do it's easy to use that for the iCloud account yourself and your personal email address for the other.

Which reminds me: don't tie your personal stuff (iCloud, purchases, whatever) to an Apple ID under your company email address. If it's stuff you should keep after leaving your current job, it should be under an Apple ID that's tied to an email address you'll still have after leaving the job. On the other hand, for things that're part of the job (e.g. apps purchased by the company for the job), it should be under an Apple ID "owned by" the company and tied to a company-controlled email address.

  pbfilter() {
      if [ $# -gt 0 ]; then
          pbpaste | "$@" | pbcopy
      else
          pbpaste | pbcopy
      fi
  }       

This version also can also act as a plain-text-only filter. If you just use `pbfilter` with no argument, it'll remove any formatting from the text in the pasteboard, leaving just straight plain text.

It does have a some limitations, though: you can't use it with an alias, or pipeline, or anything complex like that. The filter command must be a single regular command (or function) and its arguments.

Another sometimes-important difference is that if there are multiple input files, `somecommand file1 file2 file3` can tell what data is coming from which file; with `cat file1 file2 file3 | somecommand` they're all mashed together, and the program has no idea what's coming from where.

In general, though, I think it's mostly a matter of people's expertise level in using the shell. If you're a beginner, it makes sense to learn one very general way to do things (`cat |`), and use it everywhere. But as you gain expertise, you learn other ways of doing it, and will choose the best method for each specific situation. While `cat |` is usually an ok method to read from a file, it's almost never the best method, so expert shell users will almost never use it.

[1] http://redsymbol.net/articles/unofficial-bash-strict-mode/

[0] http://www-personal.umich.edu/~wmebane/inapB.pdf

[1] https://www.youtube.com/watch?v=etx0k1nLn78

Also, after turning the ignition on & back off there were a lot of (normal) transient draws (from things like the dome light that don't turn off immediately). Even with the problem circuit disconnected, it drew around 6A (!) immediately after the ignition was switched off, dropped to 0.4A after about a minute, and sat at that level for another 9 minutes before dropping again to 0.06A. That means if he hadn't waited ~10 minutes per test, he'd have been chasing draws that were actually normal.

Combine an intermittent fault with intermittent normal behavior, and you've got a troubleshooting nightmare.

[0] https://www.youtube.com/watch?v=rVScppKsfHs

That's a common misunderstanding; they filter at least 95% of particles of all sizes. It's actually intermediate-sized particles (around 0.1 - 1 micron) that're hardest to capture. Smaller particles are more subject to Brownian motion, which makes them jiggle around more, and hence makes them more likely to bump into one of the respirator's strands... where they'll stick, thanks to Van der Waals forces.

N95 masks (if properly fitted) block at least 95% of particles in that 0.1 - 1 micron range (they're tested with particles around 0.3 microns), and even higher percentages of particles that're either larger or smaller than that.

Reference: https://blogs.cdc.gov/niosh-science-blog/2009/10/14/n95/ (especially figure 2)

In any case, while gender is not directly measurable, it does seem to correlate with some aspects of brain structure. A number of studies have shown that, at least in some respects, the brain anatomy of transgender people is more similar to that of cisgender people of the same gender than those of the same sex. It's clearly more complicated than trans people having one type of brain in the other type of body, but something sort of like that is going on. See https://www.scientificamerican.com/article/is-there-somethin... and the links at https://sitn.hms.harvard.edu/flash/2016/gender-lines-science....

But whatever the basis of transgender identities is, it's clear that something real is going on. Dismissing trans people as "simply mistaken" is, well, simply mistaken.

EDIT: I should probably point out that the idea of someone developing some male-type features and some female-type should not be particularly surprising. Sexual differentiation is complex and has a lot of moving parts that don't always operate completely in sync. For example, a genetic male with complete androgen insensitivity syndrome will generally develop male-type internal organs (i.e. testes) and female-style external anatomy (a vagina, generally female appearance, etc).