Yes, it's sent to posthog.

https://en.wikipedia.org/wiki/In_the_Beginning..._Was_the_Command_Line

Look up history-search-backward in your favorite bash/readline manual.

I disagree with pretty much everything you write here, but especially this:

First of all, you have exact same amount of parens as you would in a mainstream language like Java, C, or Js.

My Perl example uses "mainstream language" syntax. Apparently that doesn't count because it's Perl (scary! mental overhead! write only!), so here's exactly the same thing in JavaScript:

function hypot(x, y) {    return Math.sqrt(x ** 2 + y ** 2);}

... or

const hypot = function (x, y) {    return Math.sqrt(x ** 2 + y ** 2);};

... or

const hypot = (x, y) => Math.sqrt(x ** 2 + y ** 2);

Note how none of these involve four layers of nested parentheses.

CPU? It's called a modem!!

Isn't that how B worked?

I am 100% confident that your claim is factually wrong.

Yeah, just don't make any mistakes and you'll be fine. Come on guys, how hard can it be?

@Tangentism @Ephera Did you mean:

echo "${var:-empty}${var:+no it aint}"

?

@masterspace

Not to be rude but not having a linter configured and running is a pretty basic issue.

Yeah, if you're a C programmer in the 1980s, maybe. But it's 2006 now and compilers are able to do basic sanity checks all on their own.

@masterspace

I haven’t used Perl though, what do you like better about it?

"Undeclared variable" is a compile-time error.

@masterspace "Undeclared variable" is a runtime error.

Perl.