As you might have noticed, Go seems to be quite the star right now. Strangely enough, I just started with it right before I suddenly heard it everywhere.

And I mean, it's a fantastic language. It was, in fact, my favorite language. Still is one of the top ones. I made a pretty huge application in it actually, which has gotten a lot of love for being from me (I'm pretty damn unknown to be honest).

So Rust then, what is it? Why am I talking about it now? Right from the start actually, my buddy @tbodt seemed fashinated about the language. None of us ever dugged very deep into it, as far as I know. I was busy with Go, pretty much.

Anyways, since I'm not professionally schooled and only a little teen hobbyist, I only just heard about data races. Of course, I hurried to update most of my applications. Including my biggest one. (All goes fine until I suddenly seem to get a goroutine leak for no apparent reason thanks to the new mutexes I put in place.)

Then I was a little bored, I looked into Rust.

My other buddy @nstafie, who I knew from the discordgo community, talked highly about it.

That's when I got into it.

Deciding to actually make a test project, I read the initial tutorial and learned as much as I could and made the tiniest test ideas I could think of.

Go vs Rust????

Remember my good ol' program that is a little buggy? I got the idea of rewriting it in Rust. Of course, I definitely wouldn't want to do that huge thing, but... yeah it was a nice thought.

Until one day, I get convinced by the discordgo community to rewrite my a little crappy code. So would I do it in Go?

Rust.

I chose Rust because it has a few tricks up it's sleeve compared to Go.

Macros. They are probably the most underrated things I've ever seen in programming. Ever wished you were able to return a function from a function? Well, macros can do just that. Plus they trade space for speed. But let's be honest, people have infinite hard drives now-a-days. Still, be careful.

Generics. This might not be something I use myself, but because of generics, it's possible for the standard library to add slightly higher functions like contains and amazing stuff.

Control. Barely any type implements the Copy "trait" (a.k.a. Rust's interface ). While this makes you pull your hair out, it also makes you aware of when copies are needed, and you can see if you can avoid them. And even if you can't, which is most of the time, you can just add .clone() .

But that wasn't the biggest reason

Compile time errors and warnings

One of the really cool things I saw when using Rust, was when I did something pretty stupid and compared if user input stored in an unsigned int was < 0 . Guess what? Rust warned me about useless check!!

One of the best advantages with compiled languages over just-in-time compiled or interpreted ones, just got a million times better. In fact, during my whole rewrite, I haven't gotten a runtime panic one single time until today (when I tried to use a function result in a macro directly... oops)

This goes to show that you suffer for your users.

Of course, I still barely understand the error messages. While they attempt to be helpful, they are still a little big and bulky, and not always really very accurate to what you want.

Go and Rust????

Don't tell me I've switched to Rust. While we both know that's true, I like to see myself as somebody who would not be afraid of switching languages per project.

Go is definitely a cool language, and is still great for a lot of things.

Go is definitely easier to understand.

Go has a lot of things built in, which Rust doesn't. The biggest missing built-in is signal handling but other missing built-ins include lazy static, http support and parsing command line arguments and JSON.

But I loved Go. What could Rust possibly have done that could make me swi-

I didn't.

You might not see it, but Rust and Go are amazingly similar compared to other languages.

Understandable type naming. Seriously, I didn't know what the difference between float and double was until Go and Rust came around and said it's f32 / float32 and f64 / float64 (where the latter is Go.)

and was until Go and Rust came around and said it's / and / (where the latter is Go.) Type AFTER the name. Not the biggest deal, but it would make sense figuring out what type a variable is after figuring out which variable.

Return type last. Same as above.

Sorry for making you read so much. Jeez!

In short, Rust is C + Go + convenience + (annoyance * 10) .

Definitely useful for anything, but not always the right language of choice.

The rewrite I were talking about can be see here

Have fun!