- 0 Posts
- 130 Comments
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())
64·12 days agoI 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.
8·22 days agoI 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
52·28 days agoWhat was the problem? I can see that if you don’t get past one of the steps described in the wiki, then you’re blocked. But I think if one has some experience with shell, CLIs and TUIs, it should be possible to follow the steps until you have a bootable system.
Is it worth it to try that, maybe through multiple attempts? Idk.
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.
Do you do that every two years?
Yes, and tar works the same, it just doesn’t handle zip files.
And even if we’re pedantic: bsdtar is Arch Linux’ executable name for a port of the
tarcommand that is shipped by BSDs, so it’s alsotar.
One example for it is … tar!
It’s insane that this isn’t consistent.
Any combination of
-h,-?and--helpexists between tools (from 0 to all 3 of them)
Why remember/include the algorithm? Tar can infer that. It’s just
bsdtar xf filename.*for everything. (bsdtar handles .zip as well)
When in doubt, blame zoom. The sheer amount of completely different outlandish weird bugs and glitches as well as the fact that they were told what the correct API for screen sharing on Linux is just for them to completely ignore that and do something weird, specific, niche and bad instead … I’ve never seen something like that since like Windows xp.
I’m completely convinced they have absolutely no idea what they’re doing on the frontend (app and web) and just have the latest newbie hire hack things together until it kinda works on their machine.
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.