This is definitely not jank.

Is it worse than Clojure?

Uh, good for you?

Okay, fair enough, you got me: I wrote his name on a piece of paper and was standing on it when I wrote that comment in order to absorb his authority. You win this Internet argument.

I was definitely not standing on the authority of Elliott, merely making use of his words and crediting him for it, so you are simply wrong.

On the contrary, quoting is exactly the act of borrowing another's idea, but doing the courtesy of giving credit to the person from whom you borrowed it.

Good writers borrow, great writers steal. -T.S. Elliot

If you have not already read through it, there is a ton of useful information about Python's data model in the user manual; it is my go-to resource when I want to do weird stuff with metaclasses and the like.

Furthermore, you might find it interesting to peruse the C code that is generated by Cython, because it gives you a concrete view of the kinds of steps that Python has to go through from a C perspective to work within its data model. (Cython is a bit faster than Python because it does not have to interpret bytecode, but unless you use special directives it still has to e.g. do general attribute lookups whenever you interact with a Python value, even if the value is an integer, and maintain reference counts.)

Finally, you might also get a lot out of skimming through the CPython bytecode instructions, as this has a lot of interesting details about how the bytecode interpreter works in practice.

I think that you may have missed the reference.

One should be wary about voting for the Alligators Eating Peoples' Faces party...

Maybe this is finally a good use for depleted uranium?

Ugh, I really hate it when people make comics like this that make it seem like solving our problems would be so simple. In the real world, where things are a lot messier, you need the blade to be at least several times higher for it to work properly!