Independently scale and deploy fridges at edge. Fridge@Edge ™

Suck it, Jian Yang

Edge devices are problematic. I want to outsource the risk and decrease capex (and just hope opex works out).

CloudFridge.

We're going to need decrease load and off-shift the munchies so the fridge doesnt crash. Can we use a CDN?

Comestible distribution network.

Cloud involves losing sovereignty of data. And rabbits.

Local Automated Refrigeration Devices Eat Rabbits.

LARDER.

sorry, us-west-1 went down for 6 hours and my milk spoiled

Definitely has "Unauthorized Bread" vibes.

Hating on Kubernetes in 2025 doesn't really dong the gong like it used to, if you want to control your workloads through a well integrated API and not be bound to a cloud vendor there aren't many realistic options.

Kubernetes is only hard because people make it hard and never bothered to understand the basics of their workload scheduler.

Kubernetes is NOT AI hype, it solves real problems for real people everywhere.

"Infrastructure projects" that are here to stay and only getting better: Linux, systemd, Postgres, Kubernetes etc...

I think a lot of the Kubernetes hate comes from non-technical people deciding to use it in cases where it either doesn't actually solve any problem, or the overhead is much greater than the benefit. There's a reason it originated from Google, and as much as it pains MBA factory graduates, the project or organizaton they manage is nowhere near Google scale.

> and as much as it pains [your average software developer], the project or organizaton they manage is nowhere near Google scale.

Fixed.