Putting software in containers is cruel and unnatural.

Programs should be allowed to roam and graze freely on computer systems. Forcibly isolating and constraining them will lead only undue suffering.

Use of technologies such as Docker in systems administration must be ended immediately, there is no ethical justification for inflicting trauma like this in an enlightened society.

In this "free range software manifesto" I will -

Muting this post immediately because I know what I've done.
This was absolutely the correct decision, Past Mike.
@mike I think I need to print this and put it on the wall at work =)
@mike were i a more malicious individual, i would add the hashtags you appear to have neglected to include

@mike I think it leads to lazy software development and systems administration. Nobody has to know how a piece of software works. And we can pretend that containerization means we don't have to worry about old and insecure dependencies.

I use containers when something is very complex to setup and I don't want to bother with it, but I try to set it up manually when I can because I get more knowledge and control.

@smeg @mike

I don't think we necessarily need to know how every random software works inside and out just to try it. But my biggest annoyance with containers is that it leads to lazier development.

What actually happens is that instead of outputting useful error messages or failing gracefully the software just crashes outright and now it's a container problem instead of "if it needs 'x' installed, why does it not check for 'x' on start" kind of problem. Things that should have been solved in the development phase now become a deployment issue; and that still doesn't stop people from packaging broken containers.

@mike

Enough of the hatred and exploitation by the segmentation typicals who preach memory and thread predictability normativity!

@mike you say your software is free yet you trap it in containers, curious.
@mike @shmouflon free range cranes, free range software
@az sanctuaries for all, even the ones they call buggy.
@mike Similarly, sandboxes are only natural for tidal- and desert-zone programs (🦀🐪).
@mike IMHO this great news needs to be re publish 1st of april.
@mike have you noticed how IT world is mad ?
Think about ecology in JVM : all that garbage collected and destroyed instead of being recycled. Zillions of bits dumped worldwide every second, destroyed instead of being reused or given to old CPUs.
@mike Also, doing tests on innocent programs held in captivity is cruel. I can't imagine what kind of monsters work I QA! Just push to production and let things sort themselves out the natural way.
@mike
Ah, unikernels ;D
@mike This, but unironically.
@mike Software is far too dangerous to be let out on its own. It should exist only on punched cards and be run as a batch job, under the close supervision on a well-trained operator.
@mike at least use KVMs so that the programs don't get claustrophobic.
@mike @foone Aren’t worms and viruses the only truly free software ? Free to live. Free to sleep on any machine they want to and wake up only to replicate passionately attaching onto any executable or library as if there was no tomorrow.
Core War - Discover the Ultimate Programming Game

Discover the world of Core War, the strategic programming game where programs battle to eliminate each other in the memory of the MARS virtual computer.

@mike GUS, wearing a tie meme: I compartmentalize my problems. You containerize your problems. We are not the same.

@mike The ethical slide started with separating processes into different address spaces.

Fun fact: all threads in the Danger OS ran in the same virtual machine! It was J*va bytecode, but still... Tagging @swetland in case he wants to chime in.

@mike I prefer to call it "Sandbox" instead of container. They are happy in there!

@mike "Abolish prisons" includes FreeBSD and fail2ban jails.

(/s)

@mike the best is to fire up a container with no open ports.. so data can get neither in nor out
@mike I got rid of endpoint protection, firewalls and user-level accounts on my network so that software could roam freely. I saw a Qakbot the other day and I thought “Yes, Nature is healing.”
@mike that's what I do! No I'm not going to tell you how many pythons I have installed.
@mike agree, additionally it leads to all this microservice waste flowing down our data streams...
@mike i only put programs in containers if they misbehave. anything else is inhumane
@mike glad to see a fellow thinker, I only consume free range software without artificial additives like GUIs. They're addictive (hence the name additives) and causes both the machine and the poor code unduly suffering.
@mike
Didn't they film a documentary about this in 1982?
@mike memory safety was a mistake. In this eSsay I wikki(((((((&&000000000000000
@mike stop “deploying” software. The software will ship when it’s good and ready and prematurely sending out in to the production leads to immature software, billions of dollars of taxpayer money needed to clean up the mess, and an entire industry built to support the therapy needed by that software rocrecover from being deployed before fully ready.

@mike this post deserves to go...

*turns around and takes off sunglasses*

... viral

@mike wait until you hear about ‘memory management units’…
@mike The Free Range Software Movement starts here.
@mike Isn’t this the plot of Tron? 😏
@mike If Stallman had written a line of code after the 2000s he'd probably actually believe this.
@mike I use docker only when programs misbehave and don't work. It's a punishment
@mike I'd argue it's more humane to give each program their own uncontested territory, with limited but reliable resources. Some programs simply take all they are given and would prey on other programs on a shared system, if set free. As the intelligent administrator, one needs to facilitate co-existence on the system despite a programs individual primal nature.