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())
I haven’t read anything this cursed in a while
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 agree with you here. As soon as you change something, that should be respected but as long as you use the default theme/wallpaper/… that could just as well mean that you prefer tracking the default or don’t care at all.
Now bringing back the explicitly disabled search bar really is atrocious
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.
Es hilft immens, damit aufzuhören, ihnen Geld in den Arsch zu schieben
If you read the article, you will see that two thirds (so also his voters) take the hush money trial seriously.
But that’s my point: instead of things weirdly not working, they will work instead.
From github’s blog:
git clone --depth=1 <url>
creates a shallow clone. These clones truncate the commit history to reduce the clone size. This creates some unexpected behavior issues, limiting which Git commands are possible. These clones also put undue stress on later fetches, so they are strongly discouraged for developer use. They are helpful for some build environments where the repository will be deleted after a single build.
Maybe the hashes aren’t different, but the important part is that comparisons beyond the fetched depth don’t work: git can’t know if a shallowly cloned repo has a common ancestor with some given commit outside the range, e.g. a tag.
Blobless clones don’t have that limitation. Git will download a hash+path for each file, but it won’t download the contents, so it still takes much less space and time.
If you want to skip all file data without any limitations, you can do git clone --filter=tree:0
which doesn’t even download the metadata
I think in this case, “depth” was am inferior solution to achieve fast cloning, that they could quickly implement. Sparse checkout (“filter”) is the good solution that only came out recently-ish
No, don’t do that. That modifies the commit hashes, so tags no longer work.
git clone --filter=blob:none
is where it’s at.
It’s pinned and !Unpin
, and only has private constructors.
Uploading is a matter of implementing Clone
A vote for a 3rd party is a vote for the opponent. Everyone says this. I simply do not buy it.
That’s the part you got wrong. The voting system means that no 3rd party has a chance. Therefore you’d effectively abstain. And that means you don’t vote to keep the candidate you hate more out of the office.
And if you really think that Trump isn’t worse in every way to your interests as a leftist, you live in a deep hole under a rock.
Trump would also support Israel. And since a third party has all the chances of a particularly small popsicle in hell, that means there’s no choice for or against supporting Israel. So you’re doing the only reasonable thing.
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.