Hmm, I could go for a Full Stack of pancakes. Though it could lead to a bloated front end…

The closest they’ve come so far is prioritizing industrial customers and compute modules for a while during a chip shortage, to my memory. Hopefully they stick to their roots in the hobbyist/educational sector.

Wait, Jai as in Jonathan Blow’s long-promised programming language? Did he finally release something after all these years? I assumed that would remain vaporware for eternity.

deleted by creator

Unless their goal is to catch common mistakes to improve their code analysis and quick fixes, in which case this plan is secretly brilliant.

I was having terrible performance problems in Windows a while back, and it turned out it had marked every drive as removable and the write cache was filling up due to an extremely slow external HDD, causing even the internal SSDs to grind to a halt until the buffer was flushed whenever a large amounts of writes were made to the HDD. Which, since the external drive was used for backups and large Steam games, was almost every other day.

If this happens often, you can disable write caching for that drive. It’ll feel slightly slower (since it’s actually operating at the speed of the hardware instead of caching operations in RAM and gradually writing them to disk in the background), but you’ll be able to remove the drive almost instantly.

This is my new favorite meme using that format. It’s perfect.

Each kernel instance can run on dedicated CPU cores while sharing the underlying hardware resources.

This sounds like a recipe for spending decades tracking down bugs and obscure race conditions. The kernel is simply too massive, and with too many vendor-specific workarounds, for them to feasibly catch and ensure compliance for every call to raw hardware.

ChatGPT

Cybersecurity

So you know how to fix all the security holes the AI left in your codebase, right? Right?

Precisely. Getting people upset is the foremost technique to farm engagement on social media. Sites such as Facebook even deliberately altered their algorithms to show content that will anger readers because it works so well to keep them invested.

Engagement bait is omnipresent and really obvious once you learn to spot it - even something as innocuous as one or two “accidental” typos in a meme to get people into the comments section.

You say “wildly wrong”, they say “incentivizing engagement”.

I’m curious why 16-bit support is being dropped. Too much additional codebase complexity for such a small use case, or are there technical reasons it’s difficult to support in a 64-bit environment that somehow don’t exist in a 32-bit one? Or is it simply not implemented yet due to a lack of dev time/interest in the feature?

I know 16-bit programs are incredibly niche these days, but I’d be way more comfortable with enterprises running their ancient software in a secure, up-to-date WINE environment as opposed to an actual Windows 3.x one with its nonexistent security. Even in an isolated VM, that kind of setup is one misconfiguration away from disaster.

The Unix epoch problem is completely unrelated to a program being 32-bit or not. The architecture affects the maximum addressable memory space, not the size of individual types. You could easily define and use a 128-bit type in a 16-bit environment, for example.

The epoch problem is simply due to a bad design call a long time ago - one that proved foundational and incredibly difficult to change once it’d become an entrenched standard. They could have made timestamps 64-bit at the time, and probably would have if they’d known their work would survive the several decades it’d take for that decision to pay off.

Except those imports were used by a huge section of code you temporarily commented out, and now you’ll need to manually select a dozen imports to get it working again when you come back to it.

(Sure you could have just commented out the unused imports, but the linter auto-sorted them and you’re feeling too lazy to copy-paste a dozen scattered lines)

When you hope they’re dyslexic and show up with delicious baklavas instead.

They might be working on an old codebase with maintainers who yell at you if you try to standardize formatting because “whitespace changes pollute diffs” (smh, programmers who don’t know how to configure their diff tools).

Someone posted this article a while back that goes into more detail on some alternatives, as well as contains one of the best and most intuitive explanations of floating point that I’ve ever read.

Don’t forget the healthy markup! It’s not a proprietary Sony storage device if they don’t charge twice as much for a tenth the space.