Right?!! Consider this - if you replace the scroll wheel with two buttons, which one would you press to scroll down?

I don’t trust them to pick good produce for me.

SO: asks a yes/no question

Me: elaborates first for 5 minutes, forgets to say yes or no

I’ve had acquaintances waste away trying to delay cancer death. Hospice is not fun, so I’d rather go out on my own terms.

Plus, any kind of money making scheme I’d think of is likely going to end up like the “aim for the bushes” scene in The Other Guys.

I cannot unhear Fishmaster.

He refers to the fact that the web app does not have default access to your device sensors, microphone, storage, etc.

Good article for discussion.

Health checks is one situation where kubernetes really shines. It makes a clear distinction between readiness probes (when the pod is ready to start serving traffic), liveness probes (when the pod should be considered dead), and startup probes (when the pod has finished bootstrapping). Coupled with autoscaling it then becomes acceptable to have a pod stop serving new traffic when it’s too busy, because other pods can be created in a short time to take the extra load.

Including backend checks in your application depends on its nature. I think the mistake that the article’s author made was not to include the checks, but to have too big of a blast radius when the check fails.

The rationale for using LTS distros is being eroded by widespread adoption of containers and approaches like flatpak and nix. Applications and services are becoming less dependent on any single distro and instead just require a skeleton core system that is easier to keep up to date. Coupled with the increased cost needed to maintain security backports we are getting to a point where it’s less risky for companies to use bleeding edge over stable.

I think the foreach one should have been recursion.