HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Rabrg
artificial-life
Python2026–2026
Rabrg / artificial-life

artificial-life

A simple (300 lines of code) reproduction of Computational Life: How Well-formed, Self-replicating Programs Emerge from Simple Interaction

2Distinct people
2Mentions
0Explicit recommenders
444GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple (300 lines of code) reproduction of Computational Life: How Well-formed, Self-replicating Programs Emerge from Simple Interaction

GitHub

Where it is used

No documented product use has been verified yet.

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 3-hour interval2 dated mentions

Observed mentions: 2026-03-08 20:42:41 UTC to 2026-03-10 19:04:24 UTC.

012026-03-08 18:00:00 UTC to 2026-03-08 21:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 8, 18:002026-03-08 21:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 00:00:00 UTC to 2026-03-09 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 03:00:00 UTC to 2026-03-09 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 06:00:00 UTC to 2026-03-09 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 09:00:00 UTC to 2026-03-09 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 12:00:00 UTC to 2026-03-09 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 15:00:00 UTC to 2026-03-09 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-09 18:00:00 UTC to 2026-03-09 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 9, 18:002026-03-09 21:00:00 UTC to 2026-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 00:00:00 UTC to 2026-03-10 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 03:00:00 UTC to 2026-03-10 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 06:00:00 UTC to 2026-03-10 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 09:00:00 UTC to 2026-03-10 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 12:00:00 UTC to 2026-03-10 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 15:00:00 UTC to 2026-03-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 18:00:00 UTC to 2026-03-10 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 10, 18:00

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
Mar 8, 18:002026-03-08 18:00:00 UTC2026-03-08 21:00:00 UTC110
Mar 8, 21:002026-03-08 21:00:00 UTC2026-03-09 00:00:00 UTC000
Mar 9, 00:002026-03-09 00:00:00 UTC2026-03-09 03:00:00 UTC000
Mar 9, 03:002026-03-09 03:00:00 UTC2026-03-09 06:00:00 UTC000
Mar 9, 06:002026-03-09 06:00:00 UTC2026-03-09 09:00:00 UTC000
Mar 9, 09:002026-03-09 09:00:00 UTC2026-03-09 12:00:00 UTC000
Mar 9, 12:002026-03-09 12:00:00 UTC2026-03-09 15:00:00 UTC000
Mar 9, 15:002026-03-09 15:00:00 UTC2026-03-09 18:00:00 UTC000
Mar 9, 18:002026-03-09 18:00:00 UTC2026-03-09 21:00:00 UTC000
Mar 9, 21:002026-03-09 21:00:00 UTC2026-03-10 00:00:00 UTC000
Mar 10, 00:002026-03-10 00:00:00 UTC2026-03-10 03:00:00 UTC000
Mar 10, 03:002026-03-10 03:00:00 UTC2026-03-10 06:00:00 UTC000
Mar 10, 06:002026-03-10 06:00:00 UTC2026-03-10 09:00:00 UTC000
Mar 10, 09:002026-03-10 09:00:00 UTC2026-03-10 12:00:00 UTC000
Mar 10, 12:002026-03-10 12:00:00 UTC2026-03-10 15:00:00 UTC000
Mar 10, 15:002026-03-10 15:00:00 UTC2026-03-10 18:00:00 UTC000
Mar 10, 18:002026-03-10 18:00:00 UTC2026-03-10 21:00:00 UTC101

What Hacker News says

2 sources
Yesterday I played around with the repo and found that (IIUC) one "environmental condition" already present in the simulation is the mutation rate. With relatively low mutation rates, I find that a whole tape filled with `<` is a good "substrate," in the sense that it can sit there stably for a long time until a random mutation puts `,` into one of its cells. Within a few generations, it will have spattered copies of the substrate into all its neighbors. Then they sit until a random mutation puts `,` into one of their cells... and so on. I described what (I think) I'm seeing in https://github.com/Rabrg/artificial-life/pull/1 , and suggested in https://github.com/Rabrg/artificial-life/pull/3 that random mutations ought to blow away the whole tape rather than modify only one cell of it. However, even with that modification to the rules, I s
Read the rest
till see the `<` substrate taking over the whole map, except when the mutation rate is very high. (I admit this doesn't make a ton of sense to me.) So, anyway, it's easy to make the mutation rate vary from one side of the map to the other. If you do that right, you can see the `<` substrate take over the low-mutation-rate side of the map, but fail to take over the higher-mutation-rate side. The `<` substrate is easy to see in the gif: it's a rapidly spreading splotch of red with gold noise flickering inside.
In Artificial-life: A simple (300 lines of code) reproduction of Computational Life

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.