jsiepkes

This about the risk of getting sued by parties with deep pockets. Antrophic is close to an IPO so that is definitely not the kind of attention they want.

> I'm not really buying that whole safe/unsafe narrative. Every language is safe if you're using it right.

Microsoft and Chromium each reported that roughly 70% of their serious security bugs were memory safety bugs. That's not a problem of beginners misusing the language. Like I said, just take a look at the Android security bulletins and count how many of these come from memory safety issues and how these numbers have improved in recent years with migrations to Rust. PHP last week? Memory safety issue.

The amount of high impact vulnerabilities coming from memory unsafe languages C and C++ proves there are too many people who "can't use it right". And these people apparently include very skilled people working at companies like Microsoft and Google on high profile projects.

We wouldn't need seatbelts if everyone would just drive safe. We wouldn't need hard hats at a construction site if everyone would just work safe.

That's kind of a weird list of languages. C and C++ are both memory unsafe languages. Every Android patch round about half of the vulnerabilities are memory safety bugs in C or C++ applications. Both Google and Microsoft independent from each other concluded that most vulnerabilities are caused by memory safety issues. Zig is also not fully memory safe and Go has a garbage collector just like Java. The Go garbage collector situation is probably worse than Java because it only has a single implementation and you have no choice. Meaning it had better fit your scenario or otherwise your screwed.

> would find any discussion based on statistically correct data of immigrants "dehumanizing"

You think the term "muselmanen" could reasonably be used in a civilized "discussion based on statistically correct data of immigrants"? You do know "muselmanen" has a very specific link to WWII concentration camps, right?

Freedom of information law's in almost all countries are about being able to access administrative documents so there can be accountability and transparency. The court ruled that a 3D scan is in this case not an administrative document.

And let's be real here; A ruling that a 3d scan of a piece of art is a "administrative document" would have been far weirder.

> How else they would force new API adoption?

And that would have been fine, if Google hadn't tried to shove the Google Play Store ecosystem down everyone's throat by throwing up barriers for side-loading apps and such.

They didn't want their tech to be used to, I don't know, blow up a school with 120 children. But did want to allow other kinds of usage. Is that so weird?

Isn't "show stopper" a bit dramatic? What is the big problem with an SSH agent? If security is a problem you should probably store your SSH keys on a HSM like a Nitrokey or Yubikey. In which case you need an agent.

Google does this as well with Google Workspace with administrators. It's super annoying.

Not checking the "audience" of a token or misconfiguring it is pretty common. A lot of applications don't actually check it.

They backtracked on "ManBearPig" (climate change) a long time ago.

But not everything needs to be directly exposed to the internet. Framework had their data leaked because their metabase instance was hacked with a zero-day. Why was it directly exposed to the Internet? Why not require the use of a VPN like a Wireguard based solution or Nebula for these "internal" kind of apps?

It's in the article; They sold gold in NYC and with that money bought gold in London.