Why do you say it's almost certainly untrue? Capital is well known for trying to suppress wages.

The amounts spent there have no practical chance of return in a reasonable timeframe. There's not that many devs that would be actually eliminated.

There's your problem! You have a theory but no proof!

Depends on the business.

I could've sworn I saw something in the last month or two about BITBLT or DirectX changes on Windows.

It wouldn't surprise me to find that Windows is now flagging and quarantining unsigned, unfamiliar executables that it catches making these draw calls or really any direct Win32 calls. Microsoft, and in particular Windows Defender which you can't really turn off anymore, has gotten pretty aggressive about blocking software for "security purposes".

Are we going from "the only stable ABI on Linux is Wine", to "the only stable ABI is Wine"?

(Especially now that .NET Framework was donated to Wine...)

> Especially now that .NET Framework was donated to Wine...

Do you mean Mono, or did I miss something?

Yes, I misremembered some things. Apparently Mono has more compatibility with .NET Framework (for instance 4.81) than dotnet (the current, modern recently released in version 10).

I mixed that up to mean that .NET Framework proper was released as open source, but that's unfortunately not the case.

Mono. Not .net fw.

This is the inverse of what he's saying. Attestation takes control away from users. Permissions give control to users. The ultimate user control is not using the software at all.

That's what the GP meant, wasn't it? "Good luck with your sandboxing, Google is already a step ahead in this cat-and-mouse game".

This article feels a little suspect. They beat the AI drum a bit hard. So I go to https://workweave.dev and of course their business model is tied up with LLMs.

> IME people an incredibly warped view of just how subtle and easy it is to introduce a memory safety bug.

Agreed, and I think part of the reason is because they take it personally when someone claims programmers (in general) can't consistently write memory safe C/C++.

Who specifically is saying this?

It's a rhetorical device. We're not meant to take it literally.

50 miles is a very long way to commute daily!

#1 does suck very much.

My solution for #2 is an sshd I start up in Termux when I need to backup. I just rsync the file onto my computer.

> With foreign key constraints, you have to delete all related records when a parent record is deleted.

I've also seen good advice that you should never delete anything from your DB, but rather put rows in a different soft-deleted state...

This was clearly not legal advice. Soft-deletes come with a lot of complexity at the application layer, more maintenance, more security risk, and require building out user data deletion processes.

Having a deleted data table is a slightly easier approach I've seen, but you still need to be aware about user and legal requirements around deleting data.

> Soft-deletes come with a lot of complexity at the application layer, more maintenance, more security risk, and require building out user data deletion processes.

That depends on your application and requirements. I've worked on situations where a soft delete, where any fields with sensitive customer data are overwritten with a placeholder or random data (for legal compliance reasons) was a lot simpler than doing a hard delete and leaving a bunch of dangling records with ids pointing to records that no longer exist.

And unless your data model is pretty simple, and you are ok with not having any kind of grace period before fully deleting user data, you'll probably need to build a user data deletion process either way.

That's fair, this can be an easier approach, however you do need to make sure that all fields get scrubbed, which can be hard to do as the codebase evolves over time and more fields or field semantics change. It may also leave a bunch of metadata – timestamps can be identifying, entity graphs can be identifying.

Exactly - there's a tension between keeping storage, performance, and cost.

Keep everything actually can make some things faster (though mostly slower) and give you a depth of information you didn't have, but has a big impact on storage and cost.

Most people pick some mix of tradeoffs - for the important things to audit keep every state change, for other ones get the backups out.