Another good tell was that this was written in 2020 and of all the things to complain about the author seems to think Swarm support is still relevant?

There are a few reasons the "IBM made them do this take" seems a bit dumb in this particular case: * Podman, CRI-O and friends were being developed in the open well before the IBM acquisition was announced much less closed. * Similarly, RHEL 8 which is when this change really happened also became generally available several months before the acquisition was announced. * The bulk of IBM advocacy seems to be pushing containerd, not podman https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.ibm.com%2Fcloud%2Fblog... It seems like the author somehow missed years of acrimony between the Docker and Red Hat folks going all the way back to ~2014 or ~2015 that led to what we see today.

This isn't actually that different from how a lot of people ended up in COBOL development, which also refuses to die. I did it for a few years straight out of university and had studied Software Eng., but I was definitely in the minority.

Luckily "Spherical Cow", which is much more sensible. won the vote for Fedora 18. http://lists.fedoraproject.org/pipermail/announce/2012-April/003067.html

How many Superjet 100s crashed on the first few take offs? 0. There had been 90 successful flights as early as 2009, let alone now.

This wasn't the first flight of this aircraft either, that was ~2008, and even on the day in question it had already done one.

The point is not to teach computer repair per se, but to ensure that users are able to repair their OLPC and thus save maintenance costs for the program as they don't have to sent someone out.

You must have missed the browser wars then.

anyone?