Video LjIe4w_-vzk

[00:00] Go versus Rust. Which is the better language to learn between Go and Rust? Which offers the best performance? Which offers the best opportunities? Which should you learn? We'll dive into all that and more. First, let me explain how we'll be approaching this. First, we'll look at the

[00:15] differences in philosophy and mindset between each language. Second, we'll explore the features of both languages and their relative strengths and weaknesses. Third, we'll examine what the statistics say about the difference between the two languages in terms of developer experience,

[00:29] attractiveness and salary. And then I'll tell you what I recommend. But whatever language you choose, I've provided links in the description to helpful resources for learning them. Let's dive in. What are the differences in philosophy between the two languages? We have our contenders. In the blue

[00:44] corner goes Friendly Gopher. In the, well, brownish red corner, Rust's unofficial mascot, Ferris the crab. And there you have it already. These logos, names, mascots and even colours tell us a lot about

[00:57] the differences between the two languages. Let's start with Go. Go's name and logo express speed and efficiency. The three lines make the text look like two wheels in rapid motion. Go's mission, as expressed by their brand book, is to bring order to the complexity of creating and running

[01:14] software at scale. Let's unpack that. Creating and running at scale. What does that mean? Go's goal is to be simple enough to be used for prototyping and efficient enough to be the language of the Go's brand book also says it wants to be thoughtful, simple, efficient, reliable,

[01:30] productive and friendly These values are expressed in the friendly cuddly mascot the gopher Russ mascot Ferris certainly has a friendly smile but it prickly though as is Russ logo Russ goal is not to be friendly

[01:44] or simple. After all, crabs walk sideways. Perhaps the best way to explain Russ's values is to tell its origin story. Graydon Hoare was a programmer at Mozilla. Coming home one night, he found an

[01:57] out-of-service elevator. He lived on the 21st floor. The software had crashed due to a memory error. This goaded horror into creating a language that prevents memory management crashes. Rust is

[02:09] designed to be solid, like the crab. And the name rust also conveys this. It doesn't refer to the oxidation of iron, but to an exceedingly resilient fungi. Now what are the differences and common

[02:21] strengths between the features of Go and Rust. Go and Rust both focus on memory management, on concurrency and performance. However, their approach is very different. This too reflects

[02:34] their philosophy. Allow me to demonstrate. First, let's talk about memory management. Go has a helpful garbage collector that tries to clean up unused memory references for you. Rust, on the other hand, enforces the concept of ownership and borrowing to prevent you from coding memory bugs.

[02:50] Go helps you, Rust forces you to do the right thing. Second, concurrency and multi-threading. In a similar fashion, Go provides easy to use Go routines. These are lightweight threads

[03:03] that allow you to write concurrent code without worrying about thread management. Rust on the other hand uses basically system threads Here Rust ownership concept helps prevent thread locking errors and data races Again Go makes your life easier Rust teaches you to do the right thing

[03:21] Third, performance. Go has a small memory footprint and is optimized for modern multi-core processors. Its syntax is simple and concise. This makes it easy to learn and to start working with.

[03:33] Go does the right thing for you by default. Rust, on the other hand, provides something called zero-cost abstractions. Basically, there is no magic. The code that you write faithfully reflects the code that the compiler produces and vice versa. This means less runtime overhead,

[03:49] which helps you build high-performance applications. In short, Go hides the complexity for you. Rust helps you understand it by exposing it. Now, what do developers think of the languages? Let's

[04:01] look at the statistics provided by the Stack Overflow Developer Survey. Go and Rust have similar popularity levels at about 13% overall among developers. Developers' opinions of the languages, however, show a difference. 84% of the developers who used Rust last year

[04:18] want to use it again this year. For Go, that number is lower at 60%. The survey also shows that 30% of those who didn't work with Rust last year want to work with it this year. That number is 20% for Go. In short, Rust is globally more desirable among developers

[04:35] than Go. But what about on the job market? Well if we look at the reported salaries, developers working in both languages report a mean yearly salary of about Go developers are slightly above and Rust developers are slightly below A word of caution here These values are reported globally The situation in your local job market will vary

[04:57] Now, after having explored the philosophies, the features and the statistics of Go and Rust, what are my recommendations? Well, let's recap. Go is designed to be simple and friendly. Rust is designed to be as hard as possible to break. They're two teachers. One is encouraging and warm,

[05:14] a kindergarten teacher. The other is demanding and harsh, a drill sergeant. One makes life easier for you. The other makes you work harder for your own good. Go and Rust also have different primary

[05:26] use cases. Go is meant for the cloud, for server applications. Rust is meant for low-level or high-performance or embedded applications. Which is the best for you? Well, that will depend on two

[05:38] things, who you are and what you're trying to build. Go is easier to pick up. Rust requires more effort but provides greater rewards in the long run. What kind of teacher do you need? Do you need encouragement? Are you building for the cloud? Well, I recommend go. Do you need a demanding

[05:56] teacher who will push you forwards? Do you want to build performance intensive or low-level embedded software? I recommend Rust. Whatever language you choose, if you're looking to pick up the basics, I recommend you go to Exorcism, which gives you simple challenges to help you

[06:11] learn. And if you're looking for projects to help you dive deep while learning how reference technologies like Git, Docker or HTTP servers work, I recommend CodeCrafters. I've provided links for both in the description. But whatever path you choose, let me know how it's going and

[06:25] I'll see you in the next video.