HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aosabook
500lines
JavaScript2014–2025
aosabook / 500lines

500lines

500 Lines or Less

36Distinct people
39Mentions
0Explicit recommenders
29.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

500 Lines or Less

GitHub

Where it is used

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

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM 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 year39 dated mentions

Observed mentions: 2014-04-17 17:54:44 UTC to 2025-02-10 12:20:28 UTC.

0369122014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC918
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC514
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC11110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC321
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

From the project README

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

Read the project’s introduction
500 Lines or Less "What I cannot create, I do not understand." -- Richard Feynman This is the source for the book 500 Lines or Less, the fourth in the Architecture of Open Source Applications series. As with other books in the series, all written material will be covered by the Creative Commons - Attribution license, and all code by the MIT License: please see the license description for details. In addition, all royalties from paid-for versions will all go to Amnesty International. The production of this book has been made possible by the financial support of PagerDuty. Mission Every architect studies family homes, apartments, schools, and other common types of buildings during her training. Equally, every programmer ought to know how a compiler turns text into instructions, how a spreadsheet updates cells, and how a database efficiently persists data. Previous books in the AOSA series have done this by describing the high-level architecture of several mature open-source projects. While the lessons learned from those stories are valuable, they are sometimes difficult to absorb for programmers who have not yet had to build anything at that scale. "500 Lines or Less" focuses on the design decisions and tradeoffs that experienced programmers make when they are writing code: Why divide the application into these particular modules with these particular interfaces? Why use inheritance here and composition there? How do we predict where our program might need to be extended, and how can we make that easy for other programmers? Each chapter consists of a walkthrough of a program that solves a canonical problem in software engineering in at most 500 source lines of code. We hope that the material in this book will help readers understand the varied approaches that engineers take when solving problems in different domains, and will serve as a basis for projects that extend or modify the contributions here. Contributors Name Affiliation Project Online GitHub Mike DiBernardo Wave editorial @mdibernardo mikedebo.ca MichaelDiBernardo Amy Brown indie editorial amyrbrown.ca @amyrbrown amyrbrown Allison Kaptur Dropbox byterun @akaptur akaptur Audrey Tang g0v.tw, Socialtext, Apple spreadsheet @audreyt audreyt Brandon Rhodes Dropbox contingent @brandon_rhodes brandon-rhodes Carl Friedrich Bolz King's College London object model cfbolz.de @cfbolz cfbolz Cate Huston   Image Filter app www.accidentallyincode.com/ @catehstn catehstn Christian Muise University of Melbourne flow-shop @cjmuise haz Daniel Jackson   same-origin-policy     Daniel Rocco BrightLink Technology contingent @drocco007 drocco007 Dann Toliver Bento Box dagoba danntoliver.com @dann dxnn Dessy Daskalov Nudge Rewards Pedometer www.dessydaskalov.com @dess_e dessy Dethe Elza   blockcode   dethe Dustin Mitchell Mozilla cluster   djmitche Erick Dransch   Modeller @ErickDransch EkkiD Eunsuk Kang   same-origin-policy     Greg Wilson   web-server @gvwilson gvwilson Guido van Rossum Dropbox crawler @gvanrossum gvanrossum A. Jesse Jiryu Davis MongoDB crawler @jessejiryudavis ajdavis Jessica Hamrick University of California, Berkeley sampler www.jesshamrick.com @jhamrick jhamrick Leah Hanson Google static analysis @astrieanna astrieanna Leo Zovic   event-web-framework     Malini Das Twitch ci malinidas.com @malinidas malini Marina Samuel Mozilla ocr www.marinasamuel.com @emtwos emtwo Ned Batchelder edX templating engine nedbatchelder.com @nedbat nedbat Santiago Perez De Rosso   same-origin-policy     Taavi Burns Previously at Points, now at PagerDuty data-store @jaaaarel taavi Yoav Rubin Microsoft In-memory functional database @yoavrubin yoavrubin Technical Reviewers Amber Yust Andrew Gwozdziewycz Andrew Kuchling Andrew Svetlov Andy Shen Anton Beloglazov Ben Trofatter Borys Pierov Carise Fernandez Charles Stanhope Chris Atlee Chris Seaton Cyryl Płotnicki-Chudyk Dan Langer Dan Shapiro David Pokorny Eric Bouwers Frederic De Groef Graham Lee Gregory Eric Sanderson James O'Beirne Jan de Baat Jana Beck Jessica McKellar Jo Van Eyck Joel Crocker Johan Thelin Johannes Fürmann John Morrissey Joseph Kaptur Josh Crompton Joshua T. Corbin Kevin Huang Maggie Zhou Marc Towler Marcin Milewski Marco Lancini Mark Reid Matthias Bussonni
Read the full README on GitHub

What Hacker News says

39 sources
https://github.com/aosabook/500lines >Each chapter consists of a walkthrough of a program that solves a canonical problem in software engineering in at most 500 source lines of code. We hope that the material in this book will help readers understand the varied approaches that engineers take when solving problems in different domains, and will serve as a basis for projects that extend or modify the contributions here.
In Tinygrad
See things like https://github.com/aosabook/500lines http://plzoo.andrej.com/ Or any somewhat readable, compact codebases. Redis, Lua, etc. Often they are pedagogical in purpose, but sometimes on accident due to ruthless factoring. No one can "learn compilers" from reading LLVM source code. But one could get the idea in a couple hours of reading http://www.iro.umontreal.ca/~felipe/IFT2030-Automne2002/Comp... And in a couple more by porting it to a new language. Think of building an exact scaled down replica of a plane or a ship before embarking on the larger version. Now build an even lighter weight model, just for learning how to build the model. This is a "fruit-fly" code.
In Great things and people that I discovered, learned, read, met, etc in 2017

Showing the 15 most recent of 39 sources. Enable JavaScript to search and browse every indexed mention.

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.