I missed Nim (2014)
So this is an old article. I wonder if his perception of Rust has changed since it&#x27;s 1.0 debut.<p>&gt; Rust is “C syntax” and Nim is Python-ish. Nim wins this one hands down for me.<p>This is always going to be a really personal choice for most people. I actually prefer all the clarity I get from the curly brackets.<p>&gt; Nim has Exceptions with tracking (!) and Rust has explicit error handling via the return value. Personally… that feels like a big step backwards, much like error handling in Go. Again, for me, a clear win for Nim. I know others feel differently, but that is ok :)<p>Rust has made a plain distinction between expected error return behavior (like parse errors) that you can recover from, and panic! which is the closest thing to exceptions. If you come from languages and code bases that suffer from huge amounts of confusion b&#x2F;c of things like RuntimeExceptions vs. CheckedExceptions vs. Errors (Java) it&#x27;s a blessing to have strongly typed return values that require doing something with the error case.<p>Though, errors in rust could be easier to work with, they are a bit painful now. It looks like there is some stuff on the road map to do just this, based on a merge I saw recently.<p>&gt; Rust is pushed by Mozilla, Nim is a grass root “true open source” language. Having a “backer” might be good, but I like grass root efforts since they tend to be more open and easier to participate in as a “full” member.<p>Mozilla is a saint for backing this effort. Love them or hate them, it&#x27;s like Redhat&#x27;s support of Linux. It&#x27;s great that there are paychecks paying for this development.<p>The Rust community is really strong, and doesn&#x27;t (IMO) suffer from the issues related to BDFL and has open transparent discussions around requested changes.