Next time, Israel might be a bit more compassionate and return smallpox-covered blankets instead of unidentified biohazards. /s

“We have thoroughly investigated ourselves and found no wrongdoing. On an unrelated note, is anybody willing to sell us some more white phosphorus?”

I’ll believe it when I see legitimate proof of it. Nothing against Tesla engineers, but “management” has historically overpromised both capabilities and timelines while simultaneously underdelivering products and fabricating evidence to their claims.

Window glass makers are going to make a fortune!

I haven’t read the white paper yet, but I really hope they only created the protocol part of this system. It’s easy enough to fuck that up alone, and even easier to fuck up crypto algorithms and their implementations.

You might want to make that conditional on videos. Racists can and do lie when making “first hand accounts.”

Because people are technologically inept and buy into the propaganda that kernel-level anticheat is more effective than the alternative solutions.

The 650 job cuts will primarily impact “corporate and supporting functions,” according to Spencer, meaning cuts to HR and marketing roles.

I was going to make a joke about HR and DEI getting the axe, but reality surpasses satire once again…

And the polluters in question are less ambiguously defined to be any company manufacturing or selling devices with lithium batteries with a capacity over 10000 MAh, of course.

If I understand correctly, Swift mentioned she didn’t have kids as a reference to Vance’s shit take on childfree individuals voting. Good ol’ Elmo just had to make it rapey.

The hotshot kubectl

alias kubectl="docker compose" ftfy

Something can be objectively correct yet still presented in an opinionated manner.

It’s not the Chromium team. Google could have added JPEG XL to Android, but that’s been stalled for nearly two years with zero explanation as for why.

The whole thing smells of managerial interference somewhere.

Interestingly, the reference implementation libjxl appears to be a Google project. They’re all over the patents file and CLA.

If Mozilla isn’t merely being hopeful about having the same team create a Rust implementation, that might actually mean there’s internal interest within Google. Assuming they pull it off, the bullshit reason for refusing to add JPEG XL to Chromium might finally stop being a blocker.

Google created the original reference implementation, libjxl. It’s not stupid that they would prefer a Rust rewrite be created by the same team.

https://github.com/libjxl/libjxl

And yet, some people vehemently refute that it’s a genocide…

Oh, don’t worry. The guy who answered vmlinuz beat me to the joke in general :)

There’s always BSD, Hurd, Darwin… or NT 🤮

The kernel. I can take or leave most things, but I’m not going back to the days of writing directly into memory-mapped registers.

That’s not the point, though. The point is to use a nominal type that asserts an invariant and make it impossible to create an instance of said type which violates the invariant.

Both validation functions and refinement types put the onus on the caller to ensure they’re not passing invalid data around, but only refinement types can guarantee it. Humans are fallible, and it’s easy to accidentally forget to put a check_if_valid() function somewhere or assume that some function earlier in the call stack did it for you.

With smart constructors and refinement types, the developer literally can’t pass an unvalidated type downstream by accident.