Blaise Agüera y Arcas implemented a computational simulation of what amounts to the RNA world hypothesis using a modified form of brainfuck language to encode the evolvable information-carrying and self-replicating substrate as executable programs:

"Computational Life: How Well-formed, Self-replicating Programs Emerge from Simple Interaction" (2024)
https://arxiv.org/abs/2406.19108

Was quite the amusing talk that he gave - and even more amusing that someone noted his paper in brainfuck's wikipedia page.

#brainfuck #RNAworld #evolution

Computational Life: How Well-formed, Self-replicating Programs Emerge from Simple Interaction

The fields of Origin of Life and Artificial Life both question what life is and how it emerges from a distinct set of "pre-life" dynamics. One common feature of most substrates where life emerges is a marked shift in dynamics when self-replication appears. While there are some hypotheses regarding how self-replicators arose in nature, we know very little about the general dynamics, computational principles, and necessary conditions for self-replicators to emerge. This is especially true on "computational substrates" where interactions involve logical, mathematical, or programming rules. In this paper we take a step towards understanding how self-replicators arise by studying several computational substrates based on various simple programming languages and machine instruction sets. We show that when random, non self-replicating programs are placed in an environment lacking any explicit fitness landscape, self-replicators tend to arise. We demonstrate how this occurs due to random interactions and self-modification, and can happen with and without background random mutations. We also show how increasingly complex dynamics continue to emerge following the rise of self-replicators. Finally, we show a counterexample of a minimalistic programming language where self-replicators are possible, but so far have not been observed to arise.

arXiv.org

Three generations of evolution: Arduino Uno, Brainfuino [-]+ Rev 1.0, and Brainfuino [-]+ Rev 1.1!

#arduino #brainfuck #retrocomputing

Ever wanted to program hardware with Brainfuck? Well now you can with Brainfuino, the only microprocessor to use this minimal programming language as its instruction set. Rev 1.1 is significantly faster than Rev 1.0, so there's no better way to run your code.

Production of Rev 1.1 is now complete and we're now selling them locally. Online orders are pre-orders for now, until local friends have been given a chance. If we have a lot of interest, we're considering another larger production run.

Credit to Matthew Archibald (@Archibald_M) for Rev 1.1 improvements and production and Eduardo and Ignacio Corpeño for Rev 1.0.

Pictured are 7x Brainfuino [-]+ Rev 1.1 complete with cases, 5x Brainfuino [-]+ Rev 1.0 PCBs, and a Sparkfun RedBoard (Arduino Uno clone) that I used for many projects in high school.

Rev 1.1 shop: https://lectronz.com/products/brainfuinov1-1
Rev 1.0 announcement: https://hackaday.com/2021/01/12/make-room-for-a-new-arduino-competitor-with-native-brainfck/

#arduino #brainfuck #retrocomputing

Estupendérrima conferencia sobre la emergencia de la vida y el modelado de la simbiogénesis. Por Agüera en la @[email protected]. // #brainfuck

RE: https://bsky.app/profile/did:plc:wge2pxx433rrmrhufniwht4i/post/3mf3nxgqwu22h

So I was at some point really into PDP-8. Single-byte instructions (8-ish of them,) 12-bit words, single register, small memory, basic drivers. Yet people managed to accomplish some really impressive feats with it, like writing an #OS. It was part of my inspiration for OS.bf in #Brainfuck.

And now that I’m eyeing this cute and super basic calculator with a single memory register, I start recalling. The days I used PDP manual as reading on the bus or in university locker rooms. The attempts to reconcile #Lisp syntax and PDP instruction set. The wish to build a computing infrastructure atop this infinitely tiny foundation.

I keep justifying this calculator purchase to myself, while I should’ve just learned #Fractran instead.

Presenting Brainfuino [-]+ Rev 1.1, the Brainfuck microcontroller!

My Christmas present from @Archibald_M has arrived! I'd been wanting a Brainfuino for years now, an Arduino-like microcontroller that only runs Brainfuck programs, but they're not sold anywhere. So, Matthew took up the challenge to understand Eduardo's design, manufacture the PCBs through JLPCB and source the parts. He even fixed some issues in the original design, like the unstable clock, and made improvements, like swapping USB Micro-B to USB-C.

We'll be selling our extra stock soon, to recoup the costs. Stay tuned.

https://github.com/kuashio/bf
https://www.hackster.io/news/eduardo-corpeno-s-brainfuino-is-an-arduino-uno-clone-programmable-only-in-brainf-k-8f3f5d69922e

#brainfuck #arduino

Going to dissect Tritium (probably the fastest #Brainfuck #compiler out there) today evening and share the findings here. I don’t expect much from that, because previous dissection attempts didn’t end resultative. But still.

Might be useful to Brainfuck / esolang optimizer / compiler folks. Including me with my Reb, a regex-driven compiler and optimizer <https://github.com/aartaka/reb>

A thread that will continue in roughly eight hours 🧵

GitHub - aartaka/reb: Regex-based toolchain for minification, compilation, optimization, and interpretation of Brainfuck code.

Regex-based toolchain for minification, compilation, optimization, and interpretation of Brainfuck code. - aartaka/reb

GitHub
Seriously tempted by #Brainfuck again. The talk of ELVM <https://github.com/shinh/elvm> from @khinsen and the memories of ed.bf are making it really hard to resist. Brainfuck is a nice language too!

Nice article on Brainfuck compiler optimization. Makes me remember when I wrote a BF interpreter in high school for my Texas Instruments Voyage 200.

http://calmerthanyouare.org/2015/01/07/optimizing-brainfuck.html

#brainfuck #esolang #compsci #compiler

brainfuck optimization strategies | matslina

Analoger geht die digitale Welt nicht, oder? Nachricht über Kontaktformulqr am Sonntag. Auto-Responder: wir sind nicht da. Schreib doch bitte Montag nochmal.

Kann mir diesen #brainfuck jemand erklären? Es muss(!) doch eine logische (rechtlich-bürokratische/arbeitnehmerrechtliche/….) Erklärung geben. Bitte 🤪 Das macht mich fertig.