HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mame
quine-relay
Ruby2013–2026
mame / quine-relay

quine-relay

An uroboros program with 100+ programming languages

93Distinct people
99Mentions
1Explicit recommenders
14.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An uroboros program with 100+ programming languages

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love his sense of humor too: https://github.com/mame/quine-relay/issues/10

minikomi used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 10:50:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year99 dated mentions

Observed mentions: 2013-07-15 14:59:43 UTC to 2026-08-07 10:01:08 UTC.

051015202013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 20 mentions; 3 submissions, 17 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 4 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 15 mentions; 5 submissions, 10 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 5 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC20317
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC211
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC743
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC15510
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC725
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC523
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC927
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1459
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC110
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC523

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Quine Relay What this is QR.rb is a Ruby program that generates a Rust program that generates a Scala program that generates ...(through 128 languages in total)... a REXX program that generates the original Ruby code again. (If you want to see the old 50-language version, see the 50 branch.) Usage Ubuntu If you are using Ubuntu 26.04 (Resolute Raccoon), you can follow these steps. 1. Install all the interpreters/compilers. First, you need to type the following apt-get command to install them all. $ sudo apt-get install afnix algol68g aspectj asymptote ats2-lang bash \ bc bsh clisp clojure cmake coffeescript crystal dc dhall \ dotnet-sdk-10.0 elixir emacs-nox erlang execline f2c fennel fish flex \ fp-compiler g++ gambas3-gb-pcre gambas3-scripter gap gawk gcc gdb gdc \ genius gforth gfortran ghc ghostscript gm2 gnat gnucobol4 gnuplot \ gobjc golang gpt groovy guile-3.0 gzip haxe icont iconx intercal \ iverilog jasmin-sable jq kotlin ksh libevent-dev libpolyml-dev \ livescript llvm lua5.3 m4 make minizinc mono-devel nasm neko nickle \ nim node-typescript nodejs ocaml octave openjdk-25-jdk pari-gp \ parser3-cgi perl php-cli pike8.0 polyml python3 r-base rakudo ratfor \ rc regina-rexx ruby ruby-mustache rustc scala scilab-cli sed slsh spin \ squirrel3 surgescript swi-prolog swiftlang tcl tcsh valac vim wabt \ xsltproc yabasic yorick zoem zsh Then, build the bundled interpreters. $ sudo apt-get install cmake libpng-dev libgd-dev libfl-dev groff bison curl $ make -C vendor 2. Run each program on each interpreter/compiler. $ ulimit -s unlimited $ ruby QR.rb > QR.rs $ rustc QR.rs && ./QR > QR.scala $ scalac QR.scala && scala QR > QR.scm $ guile QR.scm > QR.sci $ scilab-cli -nb -f QR.sci > QR.sed $ sed -E -f QR.sed QR.sed > QR.spl $ spl2c < QR.spl > QR.spl.c && gcc -z muldefs -o QR -I ./vendor/local/include -L ./vendor/local/lib QR.spl.c -lspl -lm && ./QR > QR.sl $ slsh QR.sl > QR.nut $ squirrel QR.nut > QR.sml $ polyc -o QR QR.sml && ./QR > QR.sq $ ruby vendor/subleq.rb QR.sq > QR.ss $ surgescript QR.ss > QR.swift $ swiftc QR.swift && ./QR > QR.tcl $ tclsh QR.tcl > QR.tcsh $ tcsh QR.tcsh > QR.t $ ruby vendor/thue.rb QR.t > QR.ts $ tsc --outFile QR.ts.js QR.ts && nodejs QR.ts.js > QR.unl $ ruby vendor/unlambda.rb QR.unl > QR.vala $ valac QR.vala && ./QR > QR.mid $ mono vendor/local/bin/Vlt.exe /s QR.mid && mono QR.exe > QR.v $ iverilog -o QR QR.v && ./QR -vcd-none > QR.vim $ vim -EsS QR.vim > QR.vb $ echo '<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><OutputType>Exe</OutputType><TargetFramework>net10.0</TargetFramework><EnableDefaultCompileItems>false</EnableDefaultCompileItems></PropertyGroup><ItemGroup><Compile Include="QR.vb" /></ItemGroup></Project>' > tmp.vbproj && DOTNET_NOLOGO=1 dotnet run --project tmp.vbproj > QR.wasm $ $(WASI_RUNTIME) QR.wasm > QR.wat $ wat2wasm QR.wat -o QR.wat.wasm && $(WASI_RUNTIME) QR.wat.wasm > QR.ws $ ruby vendor/whitespace.rb QR.ws > QR.xslt $ xsltproc QR.xslt > QR.yab $ yabasic QR.yab > QR.yorick $ yorick -batch QR.yorick > QR.azm $ zoem -i QR.azm > QR.zsh $ zsh QR.zsh > qr.adb $ gnatmake qr.adb && ./qr > QR.als $ LANG=C LD_LIBRARY_PATH=/usr/lib/afnix axi QR.als > QR.aheui $ ruby vendor/aheui.rb QR.aheui > QR.a68 $ a68g QR.a68 > QR.ante $ ruby vendor/ante.rb QR.ante > QR.aj $ ajc QR.aj && java QR > QR.asy $ asy QR.asy > QR.dats $ patscc -o QR QR.dats && ./QR > QR.awk $ awk -f QR.awk > QR.bash $ bash QR.bash > QR.bc $ BC_LINE_LENGTH=4000000 bc -q QR.bc > QR.bsh $ bsh QR.bsh > QR.bef $ cfunge QR.bef > QR.Blc $ ruby vendor/blc.rb < QR.Blc > QR.bf $ ruby vendor/bf.rb QR.bf > QR.c $ gcc -o QR QR.c && ./QR > QR.cpp $ g++ -o QR QR.cpp && ./QR > QR.cs $ echo '<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><OutputType>Exe</OutputType><TargetFramework>net10.0</TargetFramework><EnableDefaultCompileItems>false</EnableDefaultCompileItems></PropertyGroup><ItemGroup><Compile Include="QR.cs" /></ItemGroup></Project>' > tmp.csproj && DOTNET_NOLOGO=1 dotnet run --project tmp.csproj > QR.chef $ PERL5LIB=vendor/local/lib/perl5 compilechef QR.chef QR.chef.pl && perl QR.chef.pl > QR.clj $ clojure QR.clj > QR.cmake $ cmake -P QR.cmake > QR.cob $ cobc -O2 -x QR.cob && ./QR > QR.coffee $ coffee --nodejs --stack_size=100000 QR.coffee > QR.lisp $ clisp QR.lisp > QR.cr $ crystal QR.cr > QR.d $ gdc -o QR QR.d && ./QR > QR.dc $ dc QR.dc > QR.dhall || true $ dhall text --file QR.dhall > QR.exs $ elixir QR.exs > QR.el $ emacs -Q --script QR.el > QR.erl $ escript QR.erl > QR.e $ execlineb QR.e > QR.fsx $ echo '<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><OutputType>Exe</OutputType><TargetFramework>net10.0</TargetFramework><EnableDefaultCompileItems>false</EnableDefaultCompileItems></PropertyGroup><ItemGroup><Compile Include="QR.fsx" /></ItemGroup></Project>' > tmp.fsproj && DOTNET_NOLOGO=1 dotnet run --project tmp.fsproj > QR.false $ ruby vendor/false.rb QR.false > QR.fnl $ fennel QR.fnl > QR.fl $ flex -o QR.fl.c QR.fl && gcc -o QR QR.fl.c && ./QR > QR.fish $ fish QR.fish > QR.fs $ gforth QR.fs > QR.f $ gfortran -o QR QR.f && ./QR > QR.f90 $ gfortran -o QR QR.f90 && ./QR > QR.gbs $ gbs3 QR.gbs > QR.g $ gap -q QR.g > QR.gdb $ gdb -q -x QR.gdb > QR.gel $ genius QR.gel > QR.plt $ gnuplot QR.plt > QR.go $ go run QR.go > QR.gs $ ruby vendor/golfscript.rb QR.gs > QR.gpt $ mv QR.c QR.c.bak && gpt -t QR.c QR.gpt && gcc -o QR QR.c && ./QR > QR.grass && mv QR.c.bak QR.c $ ruby vendor/grass.rb QR.grass > QR.groovy $ groovy QR.groovy > QR.gz $ gzip -cd QR.gz > QR.hs $ rm -f QR.o && ghc QR.hs && ./QR > QR.hx $ haxe -main QR -neko QR.n && neko QR.n > QR.icn $ icont -s QR.icn && ./QR > QR.i $ ick -bfOc QR.i && gcc -std=c99 -static QR.c -I /usr/include/ick-* -o QR -lick && ./QR > QR.j $ jasmin QR.j && java QR > QR.java $ javac QR.java && java QR > QR.js $ nodejs QR.js > QR.jq $ jq -r -n -f QR.jq > QR.jsfuck $ nodejs --stack_size=100000 QR.jsfuck > QR.kt $ kotlinc QR.kt -include-runtime -d QR.jar && kotlin QR.jar > QR.ksh $ ksh QR.ksh > QR.lazy $ lazyk QR.lazy >
Read the full README on GitHub

What Hacker News says

14 sources
Read the rest
id=8602122 https://news.ycombinator.com/item?id=10719317 Not exactly what you asked for, but, some similar fun stuff.
In Time.gif (2017)
develatio·Oct 8, 2022Submission

Ask HN: How is the code from the IOCCC contest submissions shaped / indented?

Some, if not most, of the code submissions sent to IOCCC are indented / "shaped". Examples: * https://www.ioccc.org/2018/vokes/prog.c * https://www.ioccc.org/2018/yang/prog.c * https://www.ioccc.org/2018/poikola/prog.c * https://github.com/mame/quine-relay/blob/master/QR.rb How is the code of all these submissions formatted / shaped? Is it done by hand? Or is there some tool / way of automating the "shaping" of a given chunk of code?
1 points · Open discussion
This issue imploring Yusuke Endoh to write a paper about it is amusing: https://github.com/mame/quine-relay/issues/10 > p-e-w: > This is more than a cool program – it's a computer science breakthrough! Apparently, you have discovered a method for constructing quines based on an arbitrary blueprint involving any amount of languages. > > Please write a technical paper describing your approach. I'm sure you'll have no trouble finding a CS journal that will publish it. > mame: > Okay I'll submit to the Journal of Universal Rejection. Later: > mame: > I'll soon publish a book, "The world of obfuscated, esoteric, artistic programming". The book explains how to write a uroboros quine. Hence, I proudly close this issue. > It also contains my almost all (about forty) works, including alphabet-only Ruby program, radiation-hardened quine, etc., and
Read the rest
explains many techniques to write such programs. > You can buy my book on amazon.co.jp. Unfortunately, it is written in Japanese, yet another esoteric language. I hope anyone can translate to English.
In A Ruby program that generates itself through a 128-language quine loop
In this context: Saves both content and the web application itself as and output html. The wiki/app is the html file itself. If you add / remove content, you get another html file that contains the wiki app and the added / modified content. No need for complicated applications, compatible wherever a browser runs (All OS), always compatible cos html (the raw html is human readable). No proprietary format lock in. For the strict meaning: https://en.wikipedia.org/wiki/Quine_(computing) For mindblowing stuff: Quine Relay - A Ruby Program that generates Rust program that generates Scala program that generates ...(through 128 languages in total)... REXX program that generates the original Ruby code again. https://github.com/mame/quine-relay
In Feather Wiki: app for creating personal non-linear notebooks, databases, wikis
There's an interesting sentiment shared amongst some of the comments both here and in the linked thread that leetcode is somehow a fundamental measure of social worth or quality. Like, if you can complete leetcode, you're so in the in-group, if something happened to Earth tomorrow and humanity suddenly had to migrate to space, you'd definitely be on the shortlist of people $company would select to join the new colony, because you've been trialed by fire, the results have been locked in, and your value and worth will never be questioned again. At least that's my take on the perspective I'm seeing. Now, written out like that it almost seems like I'm belittling the view, but I'm caricaturizing it to call out an important distinction: Ability to complete leetcode puzzles to acquire a job has absolutely no bearing on your *social inclusion* as
Read the rest
a *person*, precisely because the initiative to mandate these tasks is coming from HR departments. And what right does HR have to dictate whether you should feel socially included or not? For that matter, what right does a workplace have to tell you that you should feel small as a person? Leetcode suffers from a sort of simplicity problem. The mental model of what leetcode implies (programming challenges) is virally straightforward to reason about both for programmers (compete! be the best! go to space one day!) and hiring managers (wow this tiny picket fence is the most effective thing I've ever been recognized for, I've made it!!). I mean that it's virally straightforward because it has a simplicity that makes it "click" for everyone in 5 seconds, which makes it easy for it to scale/spread like wildfire. And in an industry where hiring is known-ungood and everyone is grasping at straws, you can kind of see why organizations everywhere (especially the well-known, large inefficient behemoths) have adopted this on a shoo-in basis: in those environments, its user experience is orders of magnitude better than what it replaced. Here's the rub though. That simplicity I mentioned? Other comments here have talked about how leetcode only challenges a specific mindset, that it's extremely narrow. And indeed it is. It's like an IQ test. But there's something about it, a... single-minded, zen-like quality to it, like dance-pad or Tetris arcade games. In a recent thread (https://news.ycombinator.com/item?id=29728892) showcasing a multiplayer online Tetris game a lot of people marveled at how fast some players can play (the author of the site linked https://www.youtube.com/watch?v=MJDz4-pr9J4, and my personal favorite (definitely watch the end) is https://youtube.com/watch?v=lE_UHhqAd1c). These people get good not solely because of inherent talent, but because there is a catnip-like attraction that draws everyone in, and these people just keep coming back. I suspect the same is true for leetcode. People just do a Jon Skeet and keep coming back. Reminds me of "the unreasonable effectiveness of showing up every day" (https://news.ycombinator.com/item?id=27833064). However, I think that in that overwhelming one-dimensional simplicity of "leetcode means X", these finer points are completely lost in translation and do not scale. Instead we're left with "<blah> passed leetcode and got a job" and "wow this is really hard" and lots and lots of "wow I feel terrible as a person" - where that latter bit turns into what feels like an insurmountable Mr Everest because this is hard for a *lot* of people, including both those in your immediate social circle and the like-minded individuals who hang out on the same forums that you do. If you're pushing to complete these, IMHO the only context that makes sense is in an unexpected-interview-next-week sort of situation. Definitely immediate to short term. Generally speaking, if you're aiming to work somewhere this sort of thing will be valued... it doesn't really make sense to try and get your foot in the door of a marathon race by proving you can sprint, right? That's not to say that most large corporate environments actually give you work that requires a significant cross-section of this sort of skillset. In that regard leetcode is the grown-up version of "I learned all this stuff in school that I'll never use". In practice whatever real work you take on will generally be paced somewhat more sustainably and you'll have ample time to familiarize yourself with the approaches a particular piece of code uses - if they're not already in your mental toolbelt already. The simplicity of leetcode lends toward what might be described as a "false bigger picture" that describes some sort of idyllic scene where you're working on zen puzzles at work all day. You know that isn't going to happen, but it can be so easy to develop a mindset that looks at the world through leetcode glasses and says, well, what if everything I do all day does reduce down to zen puzzle solving? Yay, I get to do this forever! (Protip for ADHD hyperfocusers: observe red flag. Red flag bad. Red flag signal imminent core burnout. Hate job. Stressed out all day. Depression.) In reality, the competitive target that leetcode represents can be overwhelmingly easy to extrapolate into a whole occupation of its own. The fact that leetcode gets people jobs is 100% orthogonal to the fact that some people get stymyingly good at it like with competitive arcade games. There's probably a notable separation/distinction between people who do leetcode all day and people in Actually Interesting Positions. For example, you might've heard of the Oroboros Quine (https://github.com/mame/quine-relay), a program that emits source code in over 128 programming languages in successive steps (as you run each program, it outputs code in the next one's language) and when you finally reach the end you wind up with the original source. This person works at a Japanese company that maintains an online recipe dictionary/service. Is this a major tech company? Nope. And that's most likely the reason this person has the time to dedicate to this. They clearly have sane work-life balance. (Work isn't life, it merely sustains it.) There was a post on here recently about making a supersonic trebuchet (https://news.ycombinator.com/item?id=29408127). The author made a point that he expresssly optimized for difficulty so he would be able to control for how much time the project took. A very small pet-peeve of mine is when people say that they're passionate about working in field X or Y, as though being passionate is a critical step to solving problems. It can be, *but only if you are not emotionally investing in what you are not capable of*. The problem with passionate investment is that it can be kind of blind, like blind faith or trust - it's just, this is vaguely the right direction to go, put a moonshot amount of mental effort into it and have blind hope that something good WILL happen. (I'm reminded of a quote by a swimmer, who IIRC was asked how he won a marathon swim race. He said that he did not mentally spare any energy for the swim back.) While it is by definition pretty much impossible to have a proper cause-and-effect discussion about the efficacy of this approach, what can hold it back is being passionate about solving problems that you're fundamentally not able to just *do*. Things where you go "...wait that's actually a really interesting problem" and dwell on for hours or days or weeks because, deep down, to your brain it's not a solved problem and instead a Very Good Question. Folding back to leetcode, if you're terminally stuck, firstly you need to both identify where you're investing in what you're not capable of, and figure out what that means. While just the first half of this sentence on paper, this step may end up being a multi-month (-year?) project. It may benefit from therapy/assistance to help work through. With that done, you then need to figure out how to optimize for difficulty, possibly sourcing help to assist fighting stubbornness to solve problems the hardest possible way ("if I learn to solve this I'll be a better programmer!" - no, stop bashing your head against the wall and look at all the tomato sauce you've already gotten all over the floor; you are fallible). Finally, remember that the Zen mindset/simplicity of leetcode describes 0.01% of real work. Now have a hard think about what sorts of positions you really want. If you're saying "I don't know, something cool," then judging your abilities off of the back of leetcode is an especially significant liability, both for you (leetcode cannot provide authoritative direction about how you want to grow) and your employer (who cannot really discern any sense of what to expect from you as a person given leetcode's incredibly narrow focus as a catalyst). Seriously narrow down what you want to do - not just in terms of what sorts of programming you want to do, but what kind of environment you want. Welp, not really sure how to continue this from here so I'll stop now. I think there's a bit of projection and misinterpretation in places - I know I was envisioning a "just left school" stereotype at the end there - but hopefully parts of this are useful.
In Leetcode has taught me that I'm a bad engineer

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.