Yes, many at risk programs and housing programs and even Medicare and Medicaid provide phones and other devices to members and those device contracts with Google or via a cellular provider are for hundreds of thousands to millions of people depending on the state or federal program doing the purchasing. There isn’t a reality where those contracts will ever not be for first party devices. Even if we wanted to we couldn’t buy people one plus or other non-Google branded android devices and laptops in these programs because the companies selling them don’t meet various regulatory standards required by the programs.

These people are literally the most at risk and don’t get individual choice for their devices. The devices are being provided in the first place because too many modern systems require internet and phone access. Id.me, login.gov, MFA for your library app, your epic or Athena portals for healthcare, etc…

Where will you peer to once these laws are active everywhere. That’s where this is actually headed

Mostly not yet. They did restrict the bandwidth on relay, but anyone with half a brain can open a port and that still allows apps to direct connect without relay. Honestly I wish could just force it to never relay since randomly my iPad will use relay even when I’m on the same network but that’s more because the new iOS app since the rewrite is dogshit.

Lifetime pass since 2012 here.

Broadcom knows they bought a dying platform. Their strategy is to isolate the customers incapable of ever migrating and charge them as close to near bankruptcy as possible. They’ll get their initial return on investment in under 5 years and then eventually just let VMware die because new businesses that are still nimble all moved to other platforms anyway. They’ll hit Lotto tickets with a few whales and keep 5-10 devs on to patch stuff for those whales and print 100-1000x return on costs in perpetuity.

deleted by creator

This is why I said “most containers most of the time should”. It’s a bad practice to write to the inside of the container and a better practice to treat them as immutable. You can go as far as actively preventing them from writing to themselves when you build them or in certain container runtimes, but this is not usually how they work by default.

Also a container that is stopped and restarted will not lose its internal changes in most runtimes. The container needs to be deleted and recreated from the image to do that

Yes, technically chroot and jails are wrappers around kernel namespaces / cgroups and so is docker.

But containers were born in a post chroot era as an attempt at making the same functionality much more user friendly and focused more on bundling cgroups and namespaces into a single superset, where chroot on its own is only namespaces. This is super visible in early docker where you could not individually dial those settings. It’s still a useful way to explain containers in general in the sense that comparing two similar things helps you define both of them.

Also cgroups have evolved alongside containers at this point and work rather differently now compared to 18 years ago when cgroups were invented and this differentiation mattered more than now. We’re at the point where differentiation between VMs and Containers is getting really hard since both more and more often rely on the same kernel features that were developed in recent years on top of cgroups

A million times this. A major difference between the way most vms are run and most containers are run is:

VMs write to their own internal disk, containers should be immutable and not be able to write to their internal filesystem

You can have 100 identical containers running and if you are using your filesystem correctly only one copy of that container image is on your hard drive. You have have two nearly identical containers running and then only a small amount of the second container image (another layer) is wasting disk space

Similarly containers and VMs use memory and cpu allocations differently and they run with extremely different security and networking scopes, but that requires even more explanation and is less relevant to self hosting unless you are trying to learn this to eventually get a job in it.

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator