Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:

Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.

Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.

Yeah, but a satirical one, not one to be taken literally.

I mean, if you treat your inbox as a to-do list, that’s not that far-fetched

Wow you’re insane. “I know, I’ll discredit the woman who just pointed out that it’s hard to get credit in her field as a woman ”

Huh, I don’t get how the fairy people work.

No reason. It’s just that when there wasn’t anything to experience it, nobody asked themselves that question.

So the question is a consequence of our existence, and that’s the answer

dbg!() for Rust users

He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.

You’re right, of you have compete freedom, do that. If the place you want or need to go to is most comfortably reachable via rattlesnake road, bring boots.

In other words, if you don’t think the wasm landscape is mature enough to build a web thing with it, you are stuck with JavaScript, but you don’t have to rawdog it. I haven’t run in a single weird thing like this in years of writing typescript with the help of its type system, ESLint and a formatter.

[citation needed]

Just use a formatter. It’ll show you that the second one is two statements:

1. {} (the empty block)
2. +[] coerce an empty array to a number: new Number(new Array())

I haven’t read anything this cursed in a while

I usually write “POSIXy shell” but I thought that was clear from context this time.

The problem is that exit statuses !=0 aren’t treated as error by default (with a way to turn that off for individual expressions). Instead you have to set multiple settings and avoid certain constructs in bash/ZSH/…

Everything that works like a modern programming language by default is fine of course

Yeah, and that’s just one of many many things to consider.

As a long time former ZSH user, I’ll definitely include ZSH in shell languages to avoid for scripting.

The problem is simply the number of rules and incantations to slavishly include everywhere to make your script bail on error. set -e is not enough by far.

Python with plumbum or nushell are definitely better.

Oh you sweet summer child.

If you don’t use pipes or command substitutions, set -e gets you a fair part of the way there.

If you’re interested, I can look up the rest of the arcane incantations necessary.

Shell scripts were a mistake. The weirdness you have to remember to safely stop executing when something fails is mind-boggling.

I’m so glad nushell exists and doesn’t need any configuring to just do the reasonable thing and stop executing when something fails.

Why?

Yes only. Note that I said “new ISPs”.

The older ISPs already own all IPv4 blocks, so while they can still give them out to private or professional customers, it would be stupid to sell the blocks to competitors.

It’s becoming more and more of a problem I’d think. Blocklists just become longer, so the more an IP is used by random people the less useful it becomes.

I might be completely wrong about this though.