[phren0logy]

I'm having a hard time articulating why I think this is so fantastic. It's great to see people attack a not-so-serious problem with such gusto. I love the passion behind taking things apart just to see how things work.

Thanks, github. You made my day.

[dan00]

The value of just playing around is underestimated. A lot of discoveries have been made by people just playing around.

[cdk]

As someone with not a lot of experience in low level languages and I can't wait to play around with this. I think it will be fun way to learn and maybe even try building hardware implementation using a FPGA.

[dholowiski]

Hackaday.com will be running a competition for hardware implementations: http://hackaday.com/2012/04/08/getting-12-year-olds-to-learn...

[DanBC]

The comments link to information about the Apollo Guidance Computer.

(https://en.wikipedia.org/wiki/Apollo_Guidance_Computer)

(http://www.ibiblio.org/apollo/)

[simcop2387]

I haven't been thinking about an FPGA myself. Mostly because I don't know verilog/vhdl well enough.

I've been thinking of how hard would it be to take two 32k SRAMs and an AVR and do some fancy bank switching to handle it. I know I could probably manage it by using the onchip support directly but then I'd end up with some memory inaccessible from addressing holes.

It seems like it should be possible to do, and then it would be easy to allow real IO and everything later when that's standardized.

[Brashman]

On my list of things to get around too. I don't expect it to be too hard as it's a fairly simple processor as specced. It'll be interesting to see what architecture techniques could be added to improve things while still remaining within spec.