Goto CAN be readable, it’s true.
The problem is that it’s easy to make code that is LESS readable; in order to prevent horrible unmaintainable spaghetti, it is forbidden nearly everywhere. A lot of coding ‘rules’ are really just ways to try to cut down on stupid coding practices by greenhorns and enforce code maintainability.
That’s because it’s not. It’s ignoring the meme format and just using the image without the context.
It’s pointing out the conflict between two coding ideals - first, reducing duplicate code so that you don’t have to reinvent the wheel and/or copy-paste code (which often means making calls to libraries) which is represented by the red penguin facing right, and second, wanting to reduce dependencies so that external variables are reduced (which would mean including code in your codebase that otherwise would be an external library call) which is represented by the blue penguin facing left.
The closer you get towards one ideal, the further away you get from the other.
IF and GOTO are the only flow control we need; everything else is for cowards.
Took me a bit. I was staring at it for a while thinking ‘What part of this is socially awkward?’
Is the name of the service a reference to anything?
What happens if you run out of space because of too many uploads that are set to never expire?
(Also it’s neat! Thanks!)