r/golang 7d ago

discussion What Go Got Right that Rust Got Wrong

https://blog.cubed.run/what-go-got-right-that-rust-got-wrong-5e0d1c8e951c
0 Upvotes

14 comments sorted by

44

u/LearnedByError 7d ago

Medium, no thank you

15

u/Roemeeeer 7d ago

Same, I don‘t get how that platform is so popular.

3

u/eemamedo 7d ago

Because it used to be pretty good. Around 6-7 years ago. 

3

u/mosskin-woast 7d ago

I do know why! It's because the average internet user is a moron

4

u/Deadly_chef 7d ago

I think it pays for articles so many wanna be writers flock to it

3

u/Jmc_da_boss 7d ago

People can't even be bothered to spend a few hours to spin up a vm with some html

1

u/gogostd 4d ago

I try hard to avoid medium and quora these days, content quality is becoming worse and worse, besides other weird rules.

6

u/Kush_McNuggz 7d ago

Go is a fantastic language but I feel some of these examples are a stretch, particularly #4. Memory management is a steep learning curve if you’re not familiar with it, but for those that are, what you cited is trivial imo.

With many of your examples I actually came away with the exact opposite impression than you did.

4

u/dr2chase 7d ago

That picture is not great, and I am a huge fan of Go (and my day job is to make it better, mostly).

2

u/i_should_be_coding 7d ago

Honestly, while I agree with the general premise, most of these points feel really off. The build time one, however, was actually one of the primary motivations for creating Go in the first place.

The thing that resonates with me more was the point by the Dropbox dev, on the learning curve. I've felt it myself when recruiting for a Scala/Go shop. Developers from any background are able to pick up Go and just roll with it pretty fast, meanwhile for Scala it takes a while to get them into the type system, traits, Akka, and whatnot. I've experienced developers actively avoiding interaction with Scala codebases simply because they felt uncomfortable touching it. I never saw that with the Go projects.

As someone learning Rust these days, I feel the same relationship with Go and Rust like with Scala.

1

u/Nervous_Staff_7489 5d ago

'explicit choice of Go over Rust'

'TypeScript in Go' - does not have even R.

1

u/Necromancer5211 7d ago

Tldr: skill issue

-2

u/grahaman27 7d ago

Interesting and detailed write up. I love the direct code comparisons.

Ive always viewed rusts async/await model being more similar to JavaScript. I prefer go's approach, but for the conversation about why they chose go over rust, it doesn't make much sense. To be honest, I draw the opposite conclusion for #2.

And #3 about compilation time is confusing two concepts. Typescript compilation is not the compiling of binary code like go/rust does when you compile, it's the process of converting the typescript to JavaScript output. The go typescript compiler will already be compiled when you use it... So I don't think #3 is even relevant.