Should You Learn Rust or Golang? #programming #shorts

In this short I talk about the differences between goland and rust from a developer perspective.
which one do you like more and why?

[kcable]

I learned Rust to become a better programmer. It filled in tons of knowledge gaps and helped me learn to write better code other languages.

[brnnabee]

Man this is a hot take lol. Golang 0-90 is great, 90-100 is slow, whereas rust 0-20 is really hard but 20-100 is not only rewarding but easy. When I see takes like these I always wonder how much experience these people actually have in rust.

[ChungusTheLarge]

Rust is hard until you develop a solid understanding of ownership and lifetimes. When you have these concepts down, thinking in Rust is leaps and bounds easier _plus_ you're now using the borrow checker instead of _fighting_ it

[BboyKeny]

The most important thing is to learn what you want

[BeeBeeEight]

I don't understand, why compare apples to oranges? Go is a GCPL that compiles directly to machine code. There is currently no PL (that I know of) that does this. The closest PLs to Go are Java and C#, but they compile to bytecode first then to machine code, and they are quite or overly verbose depending on who you ask. The additional step does add overhead to compilation speed so it wouldn't be surprising if Go is faster than Java/C#. So in terms of ease of use Go is a clear winner here.

Now, Rust is a low level, non-GC PL that interacts directly with the hardware like C/C++, but unlike them Rust has memory safety due to its emphasis on ownership etc. In terms of speed Rust compares favorably with them both and it's definitely faster than Go. The GC feature is what makes Go easier to learn than Rust, but it also makes it slower than Rust. So Go and Rust can't be placed on the same pedestal, they have their own applications and set of competitors.

[michawhite]

I think it's the opposite. Going from 0-60 in Rust is hard. Going from 60-100 is easy. People who learn Javascript have to keep learning the language every single day, edge case after edge case. It's easy to do simple things. It's hard to do complex things. In Rust, it's comparatively harder to do simple things, but comparatively easy to do complex things.

[mohamadybr]

The same thing happened to me when learning the JS frameworks React and Vue! Vue was easy to learn and be good at, and React be more difficult to improve after learning the basics! BUT, the amount of information I learned and the knowledge I gained learning React was so much more and I felt like I am always challenged to become a better developer. Plus it was so much closer to vanilla JS too

[kaisadilla_phd]

The thing about Rust (and other languages that are hard because they are safe) is that it'll take longer to learn, but once you learn them, your productivity will skyrocket to levels other languages cannot achieve, because all that safety means that lots of errors that you would inadvertently introduce in a project are caught on the fly at compile time. And trust me, even the most experienced devs make mistakes - it's why we still find exploits and bugs in popular programs by bug corporations all the time.

[クールなビデオ]

Keep in mind melky have never tried to learn rust so his assessment is not the best .
Now you as student you had to learn subject that were hard, now looking back at them I think it's fair to assume that learning them was important and yielded great benefits for you .
Like imagine if some middle schooler abandoned math or physics because they were too hard, rediclous !
Learning can be uncomfortable but persistence is how you grow as person and avoiding hard problems all the time is one way to stop yourself from expanding your knowledge and limit your potential.
Rust isn't rocket science it's just a programming language as software engineer you failing to use a tool means you have work to do !

[Foulgaz]

I feel like people think Rust is harder than it is. I learned Rust having exclusively written Python prior. The compiler held my hand and it was easy to pick up in order to write some file management scripts on an HPC cluster. I, someone with no experience in compiled languages at the time, found it pretty straightforward. Fast forward a bit, and I had to pick up C for work to write firmware; C didn't hold my hand nearly as much, but my experience with Rust made it a lot more straightforward. All programming languages can get messy, but I feel like Rust has a rep for being more difficult than it really is in practice. Of course, maybe I just got lucky.

I haven't had the chance to check out Go yet, but I've been looking into it more lately; what's your favorite/least favorite part of it?

[alexrandall]

Strongly believe that you should not learn either, but particularly Rust, until you have written a reasonable amount of C/C++. You can't properly appreciate Rust's lifetime analysis, and the ways it forces you to write your code, until you properly appreciate the consequences and difficulties of not having it.

[KrishnanshAgarwal]

I believe if you know python, you should learn Rust, not Go as it will rarely change the way you think when it comes to learning, for building go with Go

[tiberiusrubicon]

True, but also two moments: First, Rust is language which can be used in a lot of different areas, you can use it from embedded to back-end development, on the other hand Go - is single purpose lang - only for Back-end(Yeah, yeah, there are libs and frameworks, which could allow to create desktop apps on go and other stuff, but all of it are not production ready)(( And at second - Go is incredibly tiny and laconic, instead of Rust. Also to start building back-end on Rust to compete with Go-lang - you would need to use a lot of libs for it, for example - pretty known and well built Actix_Web would use tokio and other libraries in it’s core, at the same time on go, you can write server even on included modules(most common way)))

[AlguienEnSuCasa]

I don't know why everyone says Go is fun... it's probably the modern language with more boilerplate I have seen

[marthinus.x]

Python: 5 minutes to learn, a lifetime to master 💀

[denissorn]

Isn't this a wrong question? People should first decide what's the thing they want to do. Design microcontrollers, hardware, write drivers for networking devices, work on a kernel, video games, do data analytics, write or design web sites or applications (business applications, trading banking etc) video games. Then start worrying about the tools. I personally don't think Rust is the best choice for someone who enjoys or wants do to web frontend or even full stack development. For a backend developer, maybe, depending on what kind of a backend for what kind of market, infra etc.

[jongeduard]

I quite recently started exploring Go and I really like it for it's simplicity. I think this is a real quality, especially because it is still strongly typed and compiled (this is good).
However, for me hardly any language can compete with Rust. Also learning Rust added more value to me as new experience, since I professionally already develop in C# already, which is also a GC language and is a still much richer language than Go, even though Go does a certain things actually better.

[suryansh]

This video popped up in my feed.
2025 I will excel in rust & solana!

[ndesimoniche]

I started programming by learning js, then react js and react native, now am learning rust and i am enjoying it, every time i am working on a js project, i now understand it better, i can pin point the abstraction that has been made in js, and it makes it fun for me, it like having super powers ❤ just my take

[SCTproductionsJ]

Could you do this 0-30, 30-60, and 60-100 comparison with each language?? Seems like a useful video!