patal

The article only considers quoted arguments. Quoting should be recommended for test, and OP probably even has a formal check for quotes being in place. However, let's just set that aside for now. Quotes are optional. And if you don't put quotes, then yes, you need to use `[ x$var = xval ]` to address empty variables.

> guaranteeing the powers of law enforcement and the judiciary to operate on the same terms as in the offline world

Have there ever been prohibitions about which encryption I can use on paper letters?

The Steve Yegge article: "Execution in the Kingdom of Nouns" serves basically as a Java joke story.

http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom...

Q: What's the difference between Ant and Maven?

A: The creator of Ant has apologized.

(https://twitter.com/technomancy/status/10994115673)

This is my experience with Jamulus, too. However, to get down to 10-40ms, you need to setup your tech as follows.

- ethernet instead of wlan

- dedicated audio interface, takes calculation overhead off your computer

- a proper microphone, improves acoustics greatly

All of these steps will increase Zoom/Skype experience, too. However, Zoom/Skype will hardly go below 100s of ms of latency, just by themselves.

That does not work so well if you're working in a team. A fairly complex regular expression is always hard to read.

We see this as early as in code review and as late as when you find a production bug because expectations of the surrounding code have changed.

For those reasons, we usually break regexes into parts anyway, and name and comment the single parts. Using the library's example, we might have:

  protocol = "^(?:http)(?:s)?"
  protocol_separator = "(?:\:\/\/)"
  url = "(?:www\.)?(?:[^\ ]*)$"
  
  regex = protocol + protocol_separator + url

Which turns out to be in the direction of these Java Verbal Expressions. I find the Verbal Expressions idea really enlightening.

> [Freud] had to return to check his results later in the year, he chanced upon a pair of furrowed organs, hidden away in the abdominal cavity, which he identified as the much-sought-after testes of a male. With the two sexes now clearly distinguished, definitive evidence of sexual reproduction had been found; and, after more than 2,000 years, Aristotle’s theory of spontaneous generation could at last be laid to rest.

It's mostly about habit. Apart from that, I really enjoy this venture into the history of 0-based vs. 1-based indexing: http://exple.tive.org/blarg/2013/10/22/citation-needed/

> the technical reason we started counting arrays at zero is that in the mid-1960’s, you could shave a few cycles off of a program’s compilation time on an IBM 7094. The social reason is that we had to save every cycle we could, because if the job didn’t finish fast it might not finish at all and you never know when you’re getting bumped off the hardware because the President of IBM just called and fuck your thesis, it’s yacht-racing time.

So it's from Fortran ;)

What's up with the layout though? For one, the text alternates between serif and sans-serif fonts, like someone came in and edited the prewritten complaint, but didn't care about formatting. Second, they have problems matching the text to the line number template, e.g. on pages 31, 38, 42, etc.

Is that common for complaints, or is this just hastily written? I remember reading others and noticed peculiar layouts there, too.

Thanks for the tip! Haven't seen this yet, and collegues complain about the MS4000's loudness when I type.

It seems that sun was feminine and the moon was masculine in Old English up to about the 16th century:

"sun (n.) [...] Old English sunne was feminine (as generally in Germanic), and the fem. pronoun was used in English until 16c.; since then masc. has prevailed." [1]

"moon (n.) [...] A masculine noun in Old English." [2]

[1] https://www.etymonline.com/search?q=sun [2] https://www.etymonline.com/search?q=moon

A lot of "dimmable" LEDs are actually shifting the flicker pattern to dim the light (shorter on phases). This is for LEDs where the user dims per remote control. OP was talking about the older "legacy" dimming, where you have a wall-mounted knob that reduces the current. Works well with incandescent bulbs. But only few LEDs support this. If they do, their internal power converter likely won't flicker, because of their more thought-out converter?

However, there are also LEDs that support legacy dimming, but again translate less current into different flicker patterns...

I thought the same. Rearing a newborn recently, I find that much of the parental/pre-parental advice works well. However, I just now realized, they probably actually understood the problems. But since only the advised actions stuck in my mind, without the problem analysis, I came to think they would act on gut feelings. I think this is sort of a child/grandchild bias.

This leaves aside parental scorn/ignorance as you describe it. Sounds like stressed-out parents, if I may say so. However, I don't know how future generations will get better at it, only that you may get better at it.

Good point. Says 2016 in the site's breadcrumb line.

Now I understand Monty Python's sketch from the Meaning of Life, where old financials pirate a multi-story building and sail it off out of town. The wikipedia article mentions that in the chapter "relocated buildings". Before I never really got the joke of that sketch.

> A high severity CVE-2017-9780 (CVSS Score 7.2) has indeed been assigned to this vulnerability. Flatpak developers consider this a minor security issue.

The flatpak release notes talk of a "minor security update", where "minor" surely means "of small size", not "of little importance" as OP would have it. Though the text could add a little importance.

> say "move, sloth" when people stand on the left side of an escalator

That's insulting everywhere. Even if there was consensus about escalator etiquette (in Europe and America), that's still needlessly offensive.

People too often assume how other people need to behave and then freak out when they don't. Apparently, japanese can assume such behaviour, at least on the escalator.

Still, throughput is higher when you have two lines standing on an escalator, instead of leaving one line open for rushers. Though throughput would be even higher, if everyone stampeded up the escalator on both lines. So how SHOULD everybody behave?

Wow, thanks for the resources! You make a convincing argument. I studied sinology, but did not go that deep into character etymology. So basically, what those writers did when they wanted to write properly, was to have the older script variants in their heads, even though the actual forms they were writing may look the same. Or rather, look the same in print and in later standards. Huh.

Thanks for clearing that up.

Are you really suggesting that writers changed hands during writing a single character? That sounds totally impractical. Also, that does not explain why there should be a different stroke order.

Do you have a source for your claim? Particularly, you're suggesting that the stroke order for the top left part was once different in China. I'd really like to see a document on this.

Three Men in a Boat, by Jerome K. Jerome

I consider this timeless humour, because it gets me to laugh out loud in public. People get startled by this. Also, I read episodes from the book to my 7 year old, who loves it. Occasionally, I need to explain a very dry joke, but some I leave for him to discover later.

Would you tag that NSFW, please?

Do you mean instance where the release number be the same, as in 1.77 vs. 2.77? Because that likely won't happen, as due to the different compatibility these should be different releases. Or do you mean, if the release numbers are reasonably close, as in 1.77 vs. 2.78, and then maybe 1.79 again?

Also shown here, although without robots: https://www.youtube.com/watch?v=SNmJqRV7LOA&t=2m18s

> Or if you have a list of 1,000,000 words, then you can use Sift to pare that down to the top 100 closest, then use Levenshtein to get the exact one.

You cannot do that, because, other than performance, Sift gives no guarantees regarding accuracy. The exact one, or rather the closest match, need not be among the 100 closest sift candidates.

I think that's a great argument. If someone mails the code, I hope to have the cleverness to suspect the encoding. However, I thought about a code repository or similar where this may be an issue, but most often is not. And I have seen some code where a wrong language character did not provoke a reasonable error, but some arbitrary parser error that went off in another line altogether (not necessarily C#).

If faced with a linter error, I don't typically delete the marked stuff, write it anew and hope fingers crossed that the error would be gone. I would try to make sense of the message, how it applies, and what the error is. At some point though, I definitely would pull my hair over a greek question mark.

"An analysis in the Harvard Business Review found generic, superficial, simplistic thinking in bullet lists widely used in business planning and corporate strategy"

I don't think this is related to bullet lists. The sentence contains the same truce if we took out the words "in bullet lists".