hkwerf

It strikes me that the former would profit from a strong type system, whereas the latter could profit from (enforced) strict aliasing.

Why exactly would it be too low-level for Rust?

I have to install an app to communicate with my child's state-sponsored daycare. I'll have to install an app to communicate with the teachers at his future school. Is this still fine?

It'd be one thing, if it were just apps. But all of these apps are essentially just containers for some web application.

Do you get access to the web application without the app? No.

So what's the point of the apps? So they can send you notifications and annoy you with irrelevant updates concerning other groups at the same daycare all day long, because they don't care to filter?

Just an FYI: If I select "Features" / "API First" on your page, I end up at a 404.

> since the daemon tries to connect to the registry with SSL

If you rewrite DNS, you should of course also have a custom CA trusted by your container engine as well as appropriate certificates and host configurations for your registry.

You'll always need to take these steps if you want to go the rewrite-DNS path for isolation from external services because some proprietary tool forces you to use those services.

I suppose they don't believe certain facts engineers are telling them. With Brexit it was coined "Project Fear". Now they're being told that adding backdoors to an encrypted service almost completely erodes trust in the encryption and, as in the case with Apple here, in the vendor. However, I suppose it is very hard to find objective facts to back this. I'd guess this is why Apple chose to both completely disable encryption and inform users about the cause.

Now we're probably just waiting for a law mandating encryption of cloud data. Let's see whether Apple will actually leave the UK market altogether or introduce a backdoor.

This is only for Docker Desktop. The Docker Engine itself is free (AFAIK). If you're on Linux, you probably don't care about Docker Desktop at all.

I get why this is annoying.

However, if you are using docker's registry without authentication and you don't want to go through the effort of adding the credentials you already have, you are essentially relying on a free service for production already, which may be pulled any time without prior notice. You are already taking the risk of a production outage. Now it's just formalized that your limit is 10 pulls per IP per hour. I don't really get how this can shift your evaluation from using (and paying for) docker's registry to paying for your own registry. It seems orthogonal to the evaluation itself.