Just use a formatter. It’ll show you that the second one is two statements:
{}(the empty block)+[]coerce an empty array to a number:new Number(new Array())
- 0 Posts
- 199 Comments
Joined 10 months ago
Cake day: September 9th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
64·7 days agoI haven’t read anything this cursed in a while
3·8 days agoGreat path, your Rust (and e.g. Python) will benefit a lot in the medium term. Medium because if you’re anytging like me, you’ll overcorrect at first and try to do everything without variables lol
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 -eis 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 -egets 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.
What’s “here”? Here in Germany, mine has it for maybe 10 years or so. Basically since launch day.
And new ISPs only have v6 since all legacy (v4) blocks have been sold years ago.
I’m not the same person, I just saw someone responding to kindness with discouragement, and humanity really doesn’t need that right now.
WTF is wrong with you. A stranger pours out their heart for you and you just stomp on it? Have the decency to just shut up and ignore it instead of going out of your way to be an asshole.
So you’re agreeing. “one does not simply stop, because one needs to be really sure that they want to stop for some reason or another”. The desire to stop doesn’t come from nothing, yet it’s the vital ingredient for stopping successfully. Unless you have it, stopping is really hard.
The contents of your message aren’t a “no”, they’re a “yes, and”
It did, wherever it’s used. If you can ditch backwards compatibility in your network and just use ipv6, everything gets so much simpler.
Nothing. It fixes the myriad of horrible hacks that are required for ipv4 to somehow still hang on.
Of course companies are sad because transition costs money, even though as usual the open source community did most of the work for them.
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.