In March, I set a lofty goal to solve 100 Project Euler problems using 100 different programming languages, all within 100 days. Slightly over 100 days later, I'll admit that I only made it slightly beyond 50, although that's not too bad considering that I quietly set this project aside a few weeks ago.

I'm not abandoning this effort, but I am definitely taking a break from it. And I'm not setting it aside because it isn't fun (though I do wonder if it's a good use of my time). At the moment, I just have more important and interesting things to attend to.

Conquests

For the record, I'd like to state that, so far, I'm most proud of the following solutions:

• SIC-1 Assembly Language, because it was hard to cram into 253 bytes
• SectorLISP, because I had to implement arithmetic twice
• Verilog, because hardware
• EXA, because Exapunks is a great game
• x86 boot sector, because I didn't want SectorLISP and SectorForth to have all the fun
• Piet, because coding in 2D, using pixels, was hard
• TypeScript's type system, because I wanted to see if it was possible (see blog post)

And a few stragglers

With all that said, there are a couple of languages I haven't yet mentioned on here:

Haxe

• I like the idea of a portable language
• But I didn't like the Java-like levels of ceremonial keywords/classes
• Having said that, I prefer Haxe's familiar syntax and conveniences over something more minimal

K

• oK is literally the only version of K I could even find
• oK also only had the only detailed documentation of K that I could find
• I'm compelled to contrast this with J (another array language), which is open source and has plenty of documentation

That's all

That was a short update, but it feels good to tie up those loose ends.