An ooc quine

👋 This page was last updated ~12 years ago. Just so you know.

Thanks to my sponsors: Jesse Luehrs, Braidon Whatley, Simon Menke, Borys Minaiev, Johnathan Pagnutti, Zachary Thomas, Herman J. Radtke III, Tyler Schmidtke, notryanb, James Leitch, Scott Sanderson, Josh Triplett, Max Heaton, Astrid, Santiago Lema, Nyefan, Daniel Wagner-Hall, Das Gürteltier, Xirvik Servers, Toon Willems and 261 more

While preparing my next post about ooc documentation yet again, I stumbled upon an old ooc quine of mine. Here it is in integrality for your pleasure:

q := 34 as Char
l := [
"q := 34 as Char"
"l := ["
"]"
"for (i in 0..2) {"
"    l[i] println()"
"}"
"for (i in 0..12) {"
"    q print(); l[i] print(); q println()"
"}"
"for (i in 2..12) {"
"    l[i] println()"
"}"
]
for (i in 0..2) {
    l[i] println()
}
for (i in 0..12) {
    q print(); l[i] print(); q println()
}
for (i in 2..12) {
    l[i] println()
}

It is very much inspired from the Wikipedia examples for a quine.

Can you find a shorter one?

Comment on /r/fasterthanlime

(JavaScript is required to see this. Or maybe my stuff broke)

Here's another article just for you:

Aiming for correctness with types

Dec 12, 2020

1 hour 32 min #javascript · #typescript · #golang · #rust

The Nature weekly journal of science was first published in 1869. And after one and a half century, it has finally completed one cycle of carcinization, by publishing an article about the Rust programming language.

It’s a really good article.

What I liked about this article is that it didn’t just talk about performance, or even just memory safety - it also talked about correctness.