Phillips/Slotted/Hex belong in the trash
Pozidriv is a bit better but most ppl damage it with a Phillips screwdriver because "it looks the same"
Torx is superior to all but very rarely used for some reason

"But Result and ? operator are so much better than errors!!!1!1!!1"
Except it gives you 0 context information or traces so gl figuring out why tf it failed
The compiler can't prevent that either

Rusts genius solution: make your code look like shit by checking/logging everywhere or install a third party package that fixes its shortcomings

@jestdotty you can still uninstall pretty much every app via adb

Or go nuts and root it

Should have just deployed shopify with a bit of customisation, easiest $5000 of your life

Reddit just has awful engineers, it's possible to achieve good performance and little js with either vanilla or frameworks

Remember the video quality picker downloads all of them at once and chooses it locally
Or the year old bug where you send a post multiple times

No password requirement is just stupid
Now someone can easily try short ones, view the email, probably login there as well with the same password

@Ranchonyx well both

the concept of minifying doesn't only apply to js, it's comparable to the strip command for native binaries

It's dean edwards packer, purpose is to compress source and not obfuscate.

That's why you can get the original source back, as opposed to "proper" obfuscators where it will only be similar at best

Off by one? Have you heard about named capture groups

@lorentz there's still a difference between looking up if a key exists and also getting it's value (additional memory accesses etc)

@AlgoRythm "unknown" instead of "any" solves that more or less

> What's the point of TypeScript's "type safety" if a Boolean variable is holding a String type
> The fact that I've to worry about this opens a whole can of worms coz now can't trust "types"

The issue is you're lying to TS in the first place with type assertions (*not* casting) or any, and then expect it to magically solve it at runtime

Fuck apt, there's also a 50% chance it will mess up the lock file
It's infinitely better on arch (+derivatives)

Why reinvent the wheel?
There are plenty of libs for parsing elf, like LIEF

Fuck rust, stopped learning it
It's being way overhyped by internet retards, almost like a cult

Lmao imagine paying for YouTube, in return they remove dislikes and make the platform worse from year to year
ublock origin + sponsorblock

Mf executes some random Chinese obfuscated jar
Wonder why it's free 🤡

I wouldn't donate a cent to Wikipedia, just look up how much money they're hoarding

Just because it's "monolithic" doesn't mean you can code
But fuck interviews regardless of that

Zed is yet another of these rust projects that only focuses on performance and forgets the actual reasons why ppl use a software
And it will be just as unresponsive once external LSP get involved

These devs then treat any external data as safe and concatenate it directly to html, surely not gonna go wrong 🤡

Sure you can maybe create a better tool suited just for your use-case
Doubt when it has to support all the shit that's requested in issues over years and having to maintain backwards compatibility

That's clearly a CI issue, .gitignore is meant for versioning and not whatever the CI copies
Can still un-ignore some dist paths
You rather want to edit .gitignore 50x in a monorepo or accidentally commit build outputs?

John Hammond isn't much better nowadays
Stretching 5 minute topics to 20 and sponsor shilling

@Kernel keeping the battery fully charged all the time will also damage it

"to avoid mitm" this was solved years ago with TLS
And to actually avoid anyone else reading it, regardless of server backdoors or hypothetical mitm: end-to-end encrypted messages

Why

@Lensflare read about IEEE754 before embarrassing yourself more

ublock origin + sponsorblock on PC, revanced on mobile
Haven't seen an ad in years