57 points speckx 1 hour ago 16 comments

bryanlarsen 36 minutes ago | parent

A standard piece of advice is that every developer should do a major project in every big language family. A Lisp, an OO language, a functional language, Prolog, VHDL or Verilog, a Forth, et cetera. They'll all make you think differently and teach you lessons you will use outside of the family.

jghn 31 minutes ago | parent

This. It's not Rust in the author's case. It's being exposed to a language that's enough different from what they're used to that it affects their big picture.

pjmlp 21 minutes ago | parent

Yes, especially since many of the type system features younger devs assign to Rust, are present in most Standard ML derived languages.

It is a scale, and there are other languages that go beyond Rust, with dependent types, effects, capabilities, linear types, formal profs,...

jahnu 19 minutes ago | parent

What counts as a major project?

kccqzy 18 minutes ago | parent

Depending on what kind of concepts you want exposure to.

If you just want generic pure computation: write an interpreter for a toy language. If it’s too large, write a macro expander that can handle C style or TeX style macros.

If you want events and concurrency: write a tmux clone that can work with multiple terminals.

If you want IO but specifically networking: write a toy HTTP server that only supports 1.0.

RussianCow 13 minutes ago | parent

I don't know if it counts as "major" to the OP, but early in my career, I wrote a Sudoku solver in several languages as part of learning them. It was just complex enough of a problem that I got a glimpse into the patterns that succeed or fail for different languages, especially when it comes to things like optimization, which is sometimes hard to observe in business applications.

treyd 12 minutes ago | parent

Could be lots of things.

A common example I give is a basic chat client/server, to learn how networking code feels, especially nonblocking IO. Especially if you're implementing the same protocol in the different languages since it means you won't necessarily be as biased by what protocol patterns are easy to implement in one language.

lnenad 17 minutes ago | parent

Agreed 100%. This is the single most useful thing I experienced in my career.

brightball 5 minutes ago | parent

100% agree with this.

Elixir was somewhere between my 12th-14th language and nothing changed my perspective so much as understanding why the BEAM works the way it does.

xeubie 10 minutes ago | parent

Rust enums conflate the tag type with the union type that uses it. These should be separate things. In the example here, you can see that Rust gives no way to represent the tag type `{Human, Cat}`. In Zig there is an enum which is a set of tags, and a union which is backed by that enum and can have fields. It is obviously better to have these as separate concepts rather than conflating them. You often want the kind without the data, and Rust gives you no way to represent it. I'm not sure why I am bothering to rant about this but it's one of my biggest annoyances with the language.

iknowstuff 5 minutes ago | parent

I think you failed the lesson of the benefit of sum types, unless I’m misunderstanding your point

coldtea 6 minutes ago | parent

Such enlightenment was a common read back in the glorious days of before 2023.

But reading this in 2026, when the entirety of the profession has changed (for better or worse) due to LLMs, seems strange.

Like someone writing how some new preservation method for making food last longer revolutionized how they manage their pantry, shortly after the invention of the fridge.

I like the post - it's just sad how many will not have these epifanies anymore, or they wont mean anything, and how many starting today would already just say "how quaint" and move on.