Type-safe lipstick :)

To offer a differing opinion, why is null helpful at all?

If you have data that may be empty, it’s better to explicitly represent that possibility with an Optional<T> generic type. This makes the API more clear, and if implicit null isn’t allowed by the language, prevents someone from passing null where a value is expected.

Or if it’s uninitialized, the data can be stored as Partial<T>, where all the fields are Optional<U>. If the type system was nominal, it would ensure that the uninitialized or partially-initialized type can’t be accidentally used where T is expected since Partial<T> != T. When the object is finally ready, have a function to convert it from Partial<T> into T.

Op: Name and shame, please.

Just in case, make sure to bring a Canadian flag pin if you go backpacking.

Being pedantic, but…

The amd64 ISA doesn’t have native 256-bit integer operations, let alone 512-bit. Those numbers you mention are for SIMD instructions, which is just 8x 32-bit integer operations running at the same time.

Only slightly related, but here’s the compiler flag to disable an arbitrary 2GB limit on x86 programs.

Finding the reason for its existence from a credible source isn’t as easy, however. If you’re fine with an explanation from StackOverflow, you can infer that it’s there because some programs treat pointers as signed integers and die horribly when anything above 7FFFFFFF gets returned by the allocator.

Only if you don’t buy the Season 1 Vault-Tec Access Pass for $49.99. Imagine not doing that and then not ever being able to get your Overpowered Armor at pass level 5. You would absolutely be ruining it for yourself by not investing into the seasonal passes.

Yeah… I think you might be an optimist. It was not the positive outcome you appeared to have taken away from it.

If you use it, your social credit score drops by 30!

I put “Messages will arrive in three to five business days” in my bio, and that solved the problem nicely. Now, I simply don’t get matches at all 😎

I’m in a small minority, but their ring0 anticheat isn’t helping with that.

That’s going to be a fun way to learn pod tolerances and affinities. Although… it’s also a great way to play around with multiarch clusters without accidentally burning a hole in your wallet from AWS/GCP usage.

giving their 1st party native apps advantageous functionality competitors can’t (yet)

Perhaps one day, other developers may be allowed into the holy land of JIT recompilation.

2024 is going to be the year of the Linux Desktop enshittification. When anything you love goes public, you won’t be loving it for much longer.

After Netflix started offering streaming, I stopped considering piracy as a worthwhile option. Now, it’s actually easier to pirate whatever the fuck you want to watch than figure out what streaming service it’s on, and which of your friends has the account you’re all sharing.

Not available anymore because we didn’t pay for licensing? Too bad, no refunds on your search.

This assumes front-end development.

From a (dev)ops perspective, if I had a vendor hand me a tarball instead of proper documentation, I’d look very far away from their company. It isn’t a matter of if shit goes wrong, but when. And when that shit goes wrong, having comprehensive documentation about the architecture and configuration is going to be a lot more useful than having to piece it together yourself in the middle of an outage.

For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen.

In that case, then yup. Fuck both the corporations patenting/paywalling these advancements and the anti-GMO crowd fear mongering about it.

Has the disease been researched well enough for us to know how to genetically engineer resistance to it? If not, what you’re saying is a moot point.