Last year I used mainly crystal. This year I’m thinking pharo smalltalk, if I can pick it up in time
I also want to do visualizations, not sure how possible that is with smalltalk.
I always use Rust, because I cannot use it at work and I am still bad with it.
New Years resolution the past 5 years: I will get better with Rust.
…and I do get better but somehow it always feels like it’s not enough. Like, I’m still an imposter.
I can program an entire embedded USB keyboard/mouse firmware from scratch that can do all sorts of things no keyboard has ever done before yet I still feel like a newbie somehow. Like there’s all these people that talk about traits and mutli-threaring with async and GPU and AI stuff and I’m like, “I wrote an embedded_hal crate that lets you use both 8 and 16-channel multiplexers simultaneously!” or, “I wrote an interface that let’s you use the extra space in your RP2040 flash memory as a filesystem!”
Yet everything I ever write in Rust always just uses the most basic and simple features because I still have trouble with complex lifetimes (passing them around quickly gets too confusing for me) and traits that work with non-basic types (because in the world of embedded
'static
is king).Good news: if you’re writing #Rust and only using basic features of the language, you’re doing it right.
People who use the advanced stuff either have unique, interesting challenges, or they’re over-engineering. Since the former are overrepresented in the blogosphere, you’re probably comparing yourself to them. But just because their problems are interesting doesn’t mean yours are not! Nor does it mean you have to use the same solutions.
If you can solve interesting problems (it sounds like you can!) and keep the code simple, more power to you!
This year I’m thinking of a real challenge and writing brainfuck with butterflies.
Or Rust. Rust is the way.
Real programmers don’t mess time messing around with butterflies or physically interacting with the world. They just intimidate the program into acting as they want through sheer fucking will
I will try to learn rust while doing it, seems like an up and coming language with some interesting features.
I never get past the first 10 days anyway due to how long they start to take and how many things are going on in December.
I hate the ones that turn out to require some niche mathematical knowledge too…
I’m going to try with an awful language so I can better criticise it in future.
Java
I like to use lisp. It is about the only time I get to use it, and I get a little better each year.
Last year i did rust and lisp both, lisp most of the time was easier.
I skipped 2023, but in 2022 I got decently far using newer Excel functions like LET and LAMBDA. And then if I could I would golf the solution into a single cell formula. Years before 2022 I used Python. I think I had more fun with Excel. Will I be up for it this year?
Going with c# again. I know the language super well but don’t often have a chance to get really deep into it with the stuff at work. These often present very non typical problems that require lesser used features.
C# is like a black hole for me. Ever since I started using it, I have been unable to really get into anything else.
If I would have learned it later, I could have learned five other languages instead ( really learned, I have still played with a bunch ).
I’d advise to pick up at least a second language for your non-critical projects. At first it feels so uncomfortable, but as you gain proficiency, you’ll see it’s a real ego boost. You realise that there really isn’t anything you can’t learn.
Thinking of using nim again like last year
Haskell! Because it fits the way I think nicely, and I don’t want to write in anything else :)
Portuguese and Gleam.
Whitespace
Probably start with Rust again this year, although it definitely makes some of the days a lot harder. I might switch to something better for quick code if I fall too far behind.
I might even try PHP - I coded it professionally at the start of my career but haven’t touched it for a decade and I’m curious to know if its improvements make it pleasant to use.
Might finally do something with Elixir. Plenty of ideas for using it with Phoenix and while I’ve seen a couple of tutorials for simple stuff like a live chat, I’ve done fuck-all thus far.
Might try V one way or another as well. Super small compiler and very small executables make me happy.
Go. I actually I haven’t written a single line of Go since last year’s AoC so it’s a good excuse to go again (pun intended).
6502 machine code
On real hardware?
It’ll definitely be running on hardware