Back to Index

quine in Constant 2018

#nmi5mgjm .anchor}
[[Method:](http://pad.constantvzw.org/p/observatory.guide.quine)
Quine]{.method .descriptor} [What: A program whose function consists of
displaying its own code. Also known as \"self-replicating
program\"]{.what .descriptor} [Why: Quines show the tension between
\"software as language\" and \"software as operation\".]{.why
.descriptor} [How: By running a quine you will get your code back. You
may do a step forward and wonder about functionality and aesthetics,
uselessness and performativity, data and code.]{.how .descriptor}
[Example: A quine (Python). When executed it outputs the same text as
the source:]{.example .descriptor}

` {.sourceCode .python}
s = 's = %r\nprint(s%%s)'
print(s%s)
`

[Example: A oneline unibash/etherpad quine, created during relearn
2017:]{.example .descriptor}

` {.quaverbatim}
wget -qO- http://192.168.73.188:9001/p/quine/export/txt | curl -F "file=@-;type=text/plain" http://192.168.73.188:9001/p/quine/import
`

[WARNING]{.warning .empty .descriptor}

The encounter with quines may deeply affect you. You may want to write
one and get lost in trying to make an ever shorter and more elegant one.
You may also take quines as point of departure or limit-ideas for
exploring software dualisms.

\"A quine is without why. It prints because it prints. It pays no
attention to itself, nor does it asks whether anyone sees it.\" \"Aquine
is aquine is aquine. \" Aquine is not a quine This is not aquine

[Remember: Although seemingly absolutely useless, quines can be used as
exploits.]{.remember .descriptor}

Exploring boundaries/tensions

databases treat their content as data (database punctualization) some
exploits manage to include operations in a database

[TODO: RELATES TO
http://pad.constantvzw.org/