Rust or Go for my next project? WHAT TO CHOOSE? (as a senior intern engineer)
AI Summary
The video helps developers decide between Go and Rust based on their goals and project type. For web servers, Go is recommended for its simplicity; for CLI apps, Rust excels. For job hunting, Go has more opportunities.
If your goal is just to learn, base the choice on the project. For web servers, Go is easy with a straightforward concurrency model. Rust is harder and may be painful for beginners.
Rust is excellent for CLI apps due to its string processing, libraries, and type system. Go is not as good in this category.
Go has many jobs, while Rust has few. Learning Go is better for getting hired at great companies.
Discord switched from Go to Rust, but it's likely a small part of their codebase. The advice may change as Rust jobs grow.
Don't pick randomly; consider your goals and project. Rust involves crying over the borrow checker and async, but it's rewarding.
Choose Go for web servers and job prospects; choose Rust for CLI applications and a deeper learning experience. Base your decision on your goals and project type.
Clickbait Check
90% Legit"Title accurately reflects content: a practical comparison of Rust vs Go based on project type and career goals."
Study Flashcards (5)
Which language is recommended for web server projects?
easy
Click to reveal answer
Which language is recommended for web server projects?
Go, because it is easy and has a straightforward concurrency model.
00:24
Which language is recommended for CLI applications?
easy
Click to reveal answer
Which language is recommended for CLI applications?
Rust, due to its string processing, libraries, and type system.
00:50
Which language has more job opportunities according to the video?
easy
Click to reveal answer
Which language has more job opportunities according to the video?
Go has tons of jobs; Rust has very few.
01:16
What company switched from Go to Rust?
medium
Click to reveal answer
What company switched from Go to Rust?
Discord.
02:06
What are the two main challenges when learning Rust mentioned in the video?
medium
Click to reveal answer
What are the two main challenges when learning Rust mentioned in the video?
The borrow checker and async programming.
02:44
🔥 Best Moments
Crab dancing song
Humorous reference to Rust's mascot and community culture.
00:12Java revolution without the Java
Clever analogy describing Go's popularity and simplicity.
01:53Crying in borrow checker and async
Memorable and humorous summary of Rust's learning curve.
02:44Full Transcript
Download .txt[00:00] It's 2022 and you want to learn a new language, but you don't really know which one to choose. Should you choose Go? Should you choose Rust? They both sound super cool. All the gophers look like they're having fun.
[00:12] The little crab dancing song is also really exciting. So which one do you choose? Well, here's the thing. It should be based off your goals and it should be based off the project. Now, if your goal is to just learn a language,
[00:24] then it should only be based off the project. If your project involves the web, some sort of server, I just highly recommend Go. It is so dang easy. The concurrency model, everything of how it works
[00:36] is just so straightforward. But if you choose Rust, it's gonna be hard. The rowing is not gonna be simple. You're gonna learn a lot, but it is gonna be painful. And if you've never done Rust before this, it will be virtually impossible to finish.
[00:50] And so I just highly recommend Go. But if you're building a CLI application, I would recommend Rust. It's such a good language for this purpose. The string processing, all the libraries that it has, it makes it so dang simple.
[01:03] Even the type system is just fantastic for this type of stuff. Whereas Go, I just don't feel like it's as good in that category. I know some people are just gonna hate that, but it's just like, that's how I feel. I think Rust is better at that.
[01:16] But if your goal is to get hired, then what language should you choose? I'd say that this is a very simple way to reason about this. What market has the most jobs?
[01:28] Rust you know there like no jobs And then there Go It has tons of jobs lots of jobs Learn Go if you trying to get hired somewhere Go is a great language to go and get a job
[01:41] to be able to actually get some experience and to be hired at pretty great companies. There are tons and tons of companies using it. It's like the Java revolution just without all the Java.
[01:53] It's fantastic. So please learn it if you're gonna try to get a job. I know that's gonna rub some people the wrong way. And I have a positive feeling like in the comments, some people are gonna be like, well, I don't know how you know this, but there's plenty of companies that are considering.
[02:06] I mean, did you know about Discord? Did you know that Discord quit? Discord, oh man, they do Discord. You know, I got it, I got it. I understand that Discord used to use Go. Now they use Rust. I'm sure it's actually a pretty small section of their code
[02:20] and it's not just bounded to their entire application. Okay, it's not that simple. So which one should you choose? Please don't just randomly pick. Don't decide beforehand, what are your goals?
[02:32] What are your building? And go from there. You know, now in one year, my advice could change. The jobs for Rust could explode and it could be a lot more useful. But this is what I think is the best advice for you.
[02:44] So go ahead, pick your language. Have a little bit of fun. I am assuming it probably will end up being go. But if you do Rust, remember, you will first cry in the borrow checker. And then after you get good at that, you will then cry in async.
[02:56] And then after you get good at that, you'll re-cry in async. Sorry, it's just how it works. Hey, that's a cool hoodie. Yes, it is. Yes, it is.