towerful

Uft, imagine if that happened and musk chose a single unicode character as the domain?!
Unicode are already sanitised from domains, because there are ubicode characters that look like - but are distinct from - ascii characters... which opens a huge pandoras box of MITM attacks of malicious sites on domains that visually look the same as legit domains.

If musk wants a single unicode character, all the browsers are going to have to figure out that can of worms

Its cheaper, has better visibility for drive health, and things like CoW means a file is extremely unlikely to be corrupt on a power failure (with hardware raid, you are relying on the battery in the raid controller for that protection. I guess you could run CoW ontop of a hardware raid). CoW also helps spread wear on SSDs.
ZFS will heal data if it finds corrupted blocks, not sure that a hardware raid does.
ZFS is the same anywhere, and is adjusted via software (as opposed to the dell PERCs which i believe require booting into essentially bios. Certainly ive never had the work through iDRAC), and you dont have to learn that raid controllers control UI (altho, they are never difficult).
Its also another part that could fail and require like-for-like replacement. ZFS on satas just needs to be able to access the drive.

I looked into it ages ago, and ZFS on HBA made so much more sense than a $300 used raid controller.

Its the DRM of shopping.
Impacts legit customers, does very little for everyone else.
After the media hype of a shoplifting crime spree hitting world wide, i imagine this is some businesses answer to that, and they managed to sell it to supermarkets

Pedestrianised areas are still accessible by emergency services.
By banning cars: public transport would still be required, deliveries would still need to be made, and i imagine there would be allowances for accessibility requirements.
Its not like cities would place down concrete blocks to entirely cut off access for all vehicles

For mass distribution of wifi APs? Some SDN solution would have a higher upfront cost but a lower running cost. Im sure all the big providers have their own system, consumer ones include ubiquiti and omada.

Cheaper than that would be mikrotik. Not really deployable at the scale of 1000s that would be required to fit every room with a wifi AP, but CAPsMAN can scale to hundreds, so still has centralised management to reduce running costs.

If it has to be cheaper still, then any cheapo SBC with wifi. While raspberry pis might fit the bill, they would be too overpowered with too many unused features to really squeeze the cost effectiveness.
Hey, its google. They could probably fork an AP into one of their home automation thingies. Then probably a whole stack of ansible scripts to try and manage 1000s of deployed linux installs

Any computer with a network port and a wifi adapter can be turned into a wifi access point.
But there are cheaper and better alternatives than a raspberry pi

I use ghcr, i have no issues pulling images from amazon ECR or wherever.
Docker got there first with the adoption and marketing.

Automation tools like ansible and terraform have existed for ages, and are great for running things without containers.
OCI just makes it a hell of a lot easier and portable

but I want to simply remind you that containers are the successor of VMs

Successor implies replacement. I think containers are another tool in the toolkit of servers/hosting, but not a replacement for VMs

IMO, Pis are for tinkering or anything that needs the GPIO.
Everything else should be some cheapo PC without the GPIO, or something embeded designed for the GPIO.
Pis are great for hobby/fun things and for prototyping.

I use proxmox to run debian VMs to run docker compose "stacks".
Some VMs are dedicated to an entire servicecs docker compose stack.
Some VMs are for a docker compose of a bunch of different services.
Some services are run across multiple nodes with HA VIPs and all that jazz for "guaranteed" uptime.
I see the guest VM as a collection, but there is only ever 1 compose file per host.
Has a bit of overhead, but makes it really easy to reason about, separate VLANs and firewall rules etc

Docker is to servers, as flatpak is to desktop apps.
I would probably run away if i saw flatpak on a headless server

his mental state prevents him from understanding the words he says

What a delightful precedent that would set