My Turing Machine

I made my own Turing Machine. Or perhaps I am a Turing Machine and I'm just looking in the mirror.

Recently, I've been reading a lot about the history of computers, and dusting up on my study of Alan Turing, who, in addition to really enjoying a children's BBC radio program me about lambs well into his 30's, also made some contributions to the theory of computation.

I took up his challenge, and decided to see if I could actually do all my work writing Ftrain on a Turing machine, so I went down to my workshop last weekend and coded my own binary-state infinite computation kernel in assembler (which is, I know, sort of cheating). Today, it runs above the Linux kernel as a virtual machine. I'm hoping to bootstrap my 400 MhZ Intel box in the next 2 weeks with the new Turing Kernel, bypassing Linux entirely.

To show you my progress, I wanted to provide some screenshots of the system's user interface, which I think is both novel and elegant. They're greatly reduced from full screen size, but I think each captures the essence of the OS very well. In case you're wondering, the input comes from hitting the space bar to represent a value of "0" and hitting the enter key to represent a value of "1." Pure interface simplicity, in under 20 bytes of code (in the future I hope to get the OS down to no more than 1 bit).

Screenshot 1: Initial Phase/Bootup

I was pretty excited when I got my Turing machine to boot for the first time and saw this screen.

Screenshot 2: The Soundex Algorithm

The system has launched and is applying a modified, internationalized version Donald Knuth's Soundex algorithm to a corpus of texts generated by a large (but not infinite) number of lemurs leaping across a 20 meter membrane Unicode keyboard. It is simultaneously running the Emacs text editor, on which I am editing this entry by referring to the binary ASCII codes for each letter and then entering them against the one-bit stack. It's all very technical, and extremely advanced stuff, so I won't keep hammering on the details.

Screenshot 3: New Color Scheme

I found the regular binary color scheme too flat, so after reading the Apple Macintosh usability guidelines, I added blue and brown and got rid of the overpowering black. Blue or brown both indicate a non-null binary value, so the basic nature of the system is preserved; the brown is just there as eye candy, like the transparent sliders on Macintosh's new "Aqua" interface. The system is computing all the primes over 5.8 × 10 in size, a computation which will take at least all the time left in the universe.

Screenshot 4: The Blue Screen of Death

On crashes, this is the standard error/debug screen. Clean interface, no bells and whistles.

Screenshot 5: Viewing the Ftrain Web Site via the Power of SMP

I wrote a beta Web browser in the last ten minutes (full ECMAScript support, no XML or CSS2 support), but found the single-bit model incredibly slow; in order to speed the process of viewing and rendering HTML pages, I'll need to operate several Turing machines in parallel, which, at a cost of $2000 per computer and due to the complexity of networking, may take some time to coordinate. The above is a simulated parallel array of Turing machines rendering this HTML page at several bits a minute (1/100th scale). In the future I may look at quantum Turing machines, which will process binary data in trillions of parallel universes at once.

That's it for now! If you'd like to contribute to the development, please drop me a line, remembering that my time is extraordinarily scarce due to my involvement in such high-level, and frankly necessary, engineering projects as this one.




Ftrain.com is the website of Paul Ford and his pseudonyms. It is showing its age. I'm rewriting the code but it's taking some time.


There is a Facebook group.


You will regret following me on Twitter here.


Enter your email address:

A TinyLetter Email Newsletter

About the author: I've been running this website from 1997. For a living I write stories and essays, program computers, edit things, and help people launch online publications. (LinkedIn). I wrote a novel. I was an editor at Harper's Magazine for five years; then I was a Contributing Editor; now I am a free agent. I was also on NPR's All Things Considered for a while. I still write for The Morning News, and some other places.

If you have any questions for me, I am very accessible by email. You can email me at ford@ftrain.com and ask me things and I will try to answer. Especially if you want to clarify something or write something critical. I am glad to clarify things so that you can disagree more effectively.


Syndicate: RSS1.0, RSS2.0
Links: RSS1.0, RSS2.0


© 1974-2011 Paul Ford


@20, by Paul Ford. Not any kind of eulogy, thanks. And no header image, either. (October 15)

Recent Offsite Work: Code and Prose. As a hobby I write. (January 14)

Rotary Dial. (August 21)

10 Timeframes. (June 20)

Facebook and Instagram: When Your Favorite App Sells Out. (April 10)

Why I Am Leaving the People of the Red Valley. (April 7)

Welcome to the Company. (September 21)

“Facebook and the Epiphanator: An End to Endings?”. Forgot to tell you about this. (July 20)

“The Age of Mechanical Reproduction”. An essay for TheMorningNews.org. (July 11)

Woods+. People call me a lot and say: What is this new thing? You're a nerd. Explain it immediately. (July 10)

Reading Tonight. Reading! (May 25)

Recorded Entertainment #2, by Paul Ford. (May 18)

Recorded Entertainment #1, by Paul Ford. (May 17)

Nanolaw with Daughter. Why privacy mattered. (May 16)

0h30m w/Photoshop, by Paul Ford. It's immediately clear to me now that I'm writing again that I need to come up with some new forms in order to have fun here—so that I can get a rhythm and know what I'm doing. One thing that works for me are time limits; pencils up, pencils down. So: Fridays, write for 30 minutes; edit for 20 minutes max; and go whip up some images if necessary, like the big crappy hand below that's all meaningful and evocative because it's retro and zoomed-in. Post it, and leave it alone. Can I do that every Friday? Yes! Will I? Maybe! But I crave that simple continuity. For today, for absolutely no reason other than that it came unbidden into my brain, the subject will be Photoshop. (Do we have a process? We have a process. It is 11:39 and...) (May 13)

That Shaggy Feeling. Soon, orphans. (May 12)

Antilunchism, by Paul Ford. Snack trams. (May 11)

Tickler File Forever, by Paul Ford. I'll have no one to blame but future me. (May 10)

Time's Inverted Index, by Paul Ford. (1) When robots write history we can get in trouble with our past selves. (2) Search-generated, "false" chrestomathies and the historical fallacy. (May 9)

Bantha Tracks. (May 5)

Tables of Contents