I was too busy to do AOC this month (that's adventofcode.com/).

So I'm thinking I'm going to do AOC 2024, *in 2025*, under the following rules:

- One challenge per week.
- I don't have to perform a challenge every week. The goal is to finish by the start of December.
- I have to do a different programming language every time.
- C, C++ and Objective-C are not eligible languages.
- If I make an honest attempt at a language and fail, I may retry in Go (but only Go) (I need to learn Go)

Bonus rules

- ASM may be used more than once as long as it targets different language families (x86_64, RISCV, ARM, WASM).
- JavaScript and TypeScript are the same language.
- Rust and Unsafe Rust may be potentially counted as two different languages.
- I may use Perl/Python to "preprocess" file inputs into arrays of numbers or strings (but no more complex parsing) in the target language
- If I make an honest attempt at a language and fail, I may retry in Go (but only Go) (I need to learn Go)

This is my list of candidate languages. ⭐ means I feel comfortable and ready to go in the language. ☆ means a language I've used but am for whatever reason not confident I could do an AOC challenge in. Totally interested in suggestions for languages I am missing from my list, opinions as to whether Scheme and Racket are the same language, etc.

Goal here is personally/professionally enriching language tourism so I can be broad minded I expect. Maybe no intentional tarpit languages this time tho.

Follow

@mcc
If you put Fortran under paelo languages you ought to specify that it has to be the 77 variant (or earlier if you really want to taste the dust).

With that label even Fortran 90 would, in my opinion, be cheating.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.