Thanks. I updated the code and the post to reflect tests for the bridge case as you mention. It affected the 12 piece and 16 piece solutions. The animated gifs are udpated and should be correct now.

Thanks for the name, I found the article here: http://blog.jgc.org/2010/01/more-fun-with-toys-ikea-lillabo-.... However, he only solves for 16 pieces. This post and program solves for any number of pieces.

You an jgc also use different criteria for symmetry/rotation removal, evidenced by different count of layouts for 16 pieces (jgc 9, you 15)

I noticed that as well, I need to figure out what is the difference ...

Good points, and I agree about understanding minimal simplicity and you don't need an OS and several layers of abstractions to blink a light. The post wasn't explicit (I think it is now after updating), but the intent was to demonstrate the variety of languages available on Linux based platforms that have GPIO SysFS, so assembly was never considered. It is more focused on those environments in which these HLL do have a role/place.

that is interesting, not sure if it is any easier than compiling some of the examples I provide, but it does open Linux platforms to those that know wiring, thanks.

Thanks, yeah, I went crazy and implemented it via go channels, which isn't a fair comparison. I updated with a slightly tweaked version of what you provided.

It wasn't clear in the original post but this was really meant for embedded Linux platforms that already have GPIO mapped via SysFS so assembly wasn't considered. I've updated the front matter of the post to reflect that. I don't know if Pascal is considered 'zing' these days, but I added that as an example. Thanks for your comment.

Writing a boolean type to SysFS/GPIO from NodeJS doesn't quite work so I tweaked your example to following similar pattern of the other languages. Thanks.

I wanted to show the power of JavaScript types, and you got a type bug? What the irony. I'll probably report that as a bug in nodejs or an undocumented "feature".

This is my favorite comment :-) After years of programming in enterprise Java, I failed to truly make it enterprise worthy! I'm going to see if I can get an assembly example added per your other comment.

Thanks, any thoughts on why I get this?

$ ghc -o blink blink.hs [1 of 1] Compiling Main ( blink.hs, blink.o )

blink.hs:7:22: parse error on input `='

Not sure; I copy-pasted it back from hackernews and it works fine for me.

you're right,fixed.