The fact it took me 20 lines of javascript to implement a nondeterministic turing machine simulatorlast week kept me up at night. All weekend. Too much code for something so simple and I kept having this gut feeling implementing a basic version shouldn’t take more than 140 bytes.

Sunday afternoon I sat down for about an hour, collected my thoughts, and started pumping out code with cryptic variable names. It was beautiful, first version was around 250 bytes, then 170, then 156, then *bam!* 133. Oh yeah baby!

function tm(I,t,e,s,i,c,k) {i=0;while(s!=e){c=t[i];k=(c)?I[s][c]:I[s].B;if(!k)return false;t.splice(i,1,k.w);i+=k.m;s=k.n;}return t;} |

I was left with a horribly looking yet simple function. All it needs are some instructions, the initial state of the tape as a list, an end state and a start state. It will return either the final tape state or false if the end state is never reached. ‘B’ is considered a blank state and the tape behaves as infinite in both directions.

If you want a file ready-made to run in node, go to my github.

Here’s a far less interesting but readable version of the same code (324 bytes):

function tm(I,tape,end,state,i,cell,current) { i = 0; while(state != end) { cell = tape[i]; current = (cell) ? I[state][cell] : I[state].B; if(!current) return false; tape.splice(i, 1, current.w); i += current.m; state = current.n; } return tape; } |

For testing I used a simple multiply program that basically turns *111* into *1110111*. For any length string of one’s. I decided to be pretty strict about inputs this time because I didn’t have the room to transform anything, so this is what the algorithm’s implementation ends up looking like

{"q0": {"1": {"w": "B", "m": 1, "n": "q1"}}, "q1": {"1": {"w": "1", "m": 1, "n": "q1"}, "0": {"w": "0", "m": 1, "n": "q2"}, "B": {"w": "0", "m": 1, "n": "q2"}}, "q2": {"1": {"w": "1", "m": 1, "n": "q2"}, "B": {"w": "1", "m": -1, "n": "q3"}}, "q3": {"1": {"w": "1", "m": -1, "n": "q3"}, "0": {"w": "0", "m": -1, "n": "q3"}, "B": {"w": "1", "m": 1, "n": "q4"}}, "q4": {"1": {"w": "B", "m": 1, "n": "q1"}, "0": {"w": "0", "m": 1, "n": "q5"}}} |

Solving this little puzzle was heaps of fun and the result is code that I would never ever want to see in production (if you code like that there is a special circle of hell for you) … now I’m just left wondering if there’s a smaller solution in a less verbose language. Can it be made so small I could tweet “Turing Machine: <code>”?

Food for thought.

PS: the shortest solution by subzey in 79 bytes

function(a,b,c,d,e){for(e=0;d<c;)with(a[d][b[e]||"B"])b[e]=w,e+=m,d=n;return b} |

###### Related articles

- Nondeterministic turing machine simulator in 23 lines of JavaScript (swizec.com)
- Is turing machine is a real device or an imaginary concept? (stackoverflow.com)
- Turing completeness bullshit (shebang.ws)
- The Brainfu*k Turing Machine (Javascript) (work.damow.net)

### Learned something new? Want to improve your skills?

Join **over 10,000 engineers** just like you already improving their skills!

Here's how it works 👇

Leave your email and I'll send you an **Interactive Modern JavaScript Cheatsheet 📖**right away. After that you'll get thoughtfully written emails every week about **React, JavaScript**, and **your career**. Lessons learned over my 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

PS: You should also follow me on twitter 👉 here.

It's where I go to shoot the shit about programming.