qvib.pro
RU

5 weirdest repos on GitHub

A code-free repo, digitized Apollo 11 flight software, a Schwarzenegger-quotes language, and an emoji-only one — what they are and why they matter.

open-source бесплатно base

Репозиторий nocode задокументировал принцип «лучший код — никакой код»: README без кода, тысячи звёзд и открытых issues на GitHub checked 2026-07-16

Updated: 16.07.2026

Open source ↗

5 weirdest repos on GitHub

GitHub is not only working libraries and frameworks. Some of the most starred repositories exist for a joke, a philosophical statement or a historical archive. Going through five of them is not purely entertainment: reading unusual code and getting an AI to explain how it works is prompt engineering practice too.

1. nocode — a repository without a single line of code

github.com/kelseyhightower/nocode proves its point literally: a README, an empty repository and no code inside — because "the best code is no code at all". The project has 65 thousand stars, 4.2 thousand open issues and 488 pull requests — all into the void, and all clearly in on the joke.

Why look: it is a pure example of viral open-source humor, worth understanding when you read other people's READMEs — not everything in a repository is meant literally.

2. Apollo-11 — the flight computer source code of the Moon mission

github.com/chrislgarry/Apollo-11 is the digitized source code of the Apollo Guidance Computer, the onboard computer of the 1969 mission that carried the astronauts to the Moon. It is written in assembly and was restored from physical printouts in the MIT Museum archive.

Why look: a rare chance to see real low-level code from the 1960s — the memory and performance limits of the era forced people to write extremely compact and reliable code. A useful contrast to modern development with near-unlimited resources.

3. ArnoldC — a programming language built from Schwarzenegger quotes

github.com/lhartikk/ArnoldC replaces the language keywords with lines from Arnold Schwarzenegger movies: IT'S SHOWTIME starts the program, TALK TO THE HAND prints text, YOU HAVE BEEN TERMINATED ends it. This is not a mock-up — the language compiles and actually runs programs.

Why look: esoteric languages like ArnoldC are a good way to understand what a programming language is even made of (lexer, parser, interpreter), because the syntax is deliberately absurd and stops distracting you from the structure.

4. emojicode — a programming language written in emoji

github.com/emojicode/emojicode is a full language where all the code is written in emoji instead of letters. It supports classes, generics, closures and optional types — comparable in capability to ordinary general-purpose languages, just with a different set of symbols instead of keywords.

Why look: it shows that language syntax is largely a convention; the logic of programming itself (types, classes, control flow) does not depend on the alphabet it is written in.

5. rickrollrc — a rickroll right in the terminal

github.com/keroserene/rickrollrc is a bash script that plays the Never Gonna Give You Up video right in the terminal: frames are rendered with ANSI 256-color sequences and UTF-8 characters, and the sound plays if a player is available. There is an inject mode that writes a call to the script into .bashrc.

Why look: a vivid demonstration that the terminal can render far more than text — the same ANSI rendering principle powers legitimate tools like progress bars and charts right in the console.

What to take away for your own practice

All five are technically interesting, but for different reasons. Open ArnoldC and emojicode if you want to understand how a compiler or interpreter is built — their sources are compact and readable. Apollo-11 is material for understanding the history of low-level code. nocode and rickrollrc are more the cultural context of the open-source community, useful to know when you run into similar humor in someone else's repository.

How we do it

In the qvib.pro knowledge base, breakdowns of unusual repositories like these double as prompt engineering exercises: asking Claude to explain unfamiliar code line by line, to find patterns in the architecture, or to rewrite an esoteric example in an ordinary language is a working way to build the skill of reading other people's code with AI, not only writing your own.

  • The "Vibe coding" section: qvib.pro/arsenal/vibe-coding-tools-github/
  • Prompts for code review and refactoring: qvib.pro/arsenal/prompts/code-review-i-refaktoring/
  • How the qvib engine works: qvib.pro/

Читать по-русски →