https://www.theguardian.com/world/2019/sep/23/china-footage-reveals-hundreds-of-blindfolded-and-shackled-prisoners-uighur

One isn’t a corrupt dictator killing or imprisoning anyone who complains about him. If you think the little guy isn’t getting hurt in China I want the drugs you’re on.

Ah today’s bothsidesism

This aircraft predates most of the issues. I suspect FedEx cheaped on maintanance.

Why yes, I would like my stack traces to make no ffing sense! I’m so glad you asked.

I wouldn’t trust the Java app sandbox at all. They basically abandoned it.

It’s probably confusing people already who never rented VHS tapes

Honestly it got pretty visible during the height of the covid pandemic: https://apnews.com/article/coronavirus-pandemic-health-68c9762a4420094d300f9cbada0186f8

Not sure how much worse you could make it.

Not a JS dev either but ===.

Not really sure what the (+x) is about

I use Gorillas with Grandparents instead as the performance is much better. Do you know how bad Gumbies looks on your resume? It came out in 2022.

The thing is the whole c program is unsafe. In rust individual parts are marked unsafe. This means auditing should be easier. Also being always on your toes isn’t really viable. Breaking down the program into safe vs unsafe is probably an improvment

In cases where bugs have been counted they tended to make up the majority of vulnerabilities. Chrome, Firefox, and Windows reported that around 70% of security vulnerabilites were memory corruption. Yes a subset, but the majority of the worst subset.

Oh look the gold bugs are back

Those are Mayan numerals for those curious

Apple wrote bugged TLS code that broke using unbraced ifs with a goto, hence the name “goto fail”. You don’t need a goto to break this code though. All you need is a second indented line under the if

#2 is also the most insideous to update. Add another indented line to one of the conditions and the cotrol flow completely breaks while visually appearing fine.

C and a number of other languages have annoying pair of parallel syntax systems that makes it easy for people to read code one way and computers to compile it another. People read the indentation and newlines while compilers count braces and semicolons. #2 gets rid of the braces and makes control flow driven by semicolons making human visual inspection more likely to fail

Please don’t use #2. It is how you get the goto fail bug

As someone who has had to put together websites:

• It is supported by every major browser
• It is halving the amount of your mobile data that I am using sending you images (With lossy compression it does even better)
• It is decreasing my network egress costs
• It is increasing the number of connections I can serve in a given time period

Nope I am not going to stop using this or AVIF (which does better)

The article doesn’t count the popups you get when you try to change your default browser

While that is an interesting idea I suspect the actual reason is their efforts to get it FDA certified as a medical device (which still hasn’t happened). The current app makes it abundantly clear it is not currently certified and a third party app claiming otherwise might be a liability concern.