@angeliliev7880

Rust has amazing performance when you get it right (which is hard). Go has good performance and you don’t even have to try that hard for it

@__jan

The Rust code has a shared HashMap behind a mutex. That's most of the problem... You're completely removing any benefit of multithreading, because your other threads can't do any work when the HashMap is in use (which is all the time). You could try changing it for an RwLock, because most of the time, you seem to be only reading from it. Another option is to use a concurrent hashmap, like DashMap, which tries to be an easy replacement for RwLock<HashMap>.

Other (less important) issues are: You're heap-allocating all of your futures from Listenable because of async_trait, and you're spawning two tasks instead of one per connection, increasing pressure on the task scheduler.

@fedeanastasis7040

In my previous job i got a little exposure to Go and i really liked. This kind of informative videos solidify my decision to get better at Go and have the right tool for the right job (because getting to work in Kotlin backend outside of android apps is going to be really hard)

@mhmmdshaz98

I'm more impressed with the tests you plan and write to make these comparisons than the actual results. I am baffled by the amount of time and work you just put into stuff like these. And the best part is, you do this because you're just crazy and love shit like this. 
Love your videos man, inspiring .❤️.

@Hedshodd

Hm, I'm actually not immensely surprised about the comparison between Rust and Go in the end with Go being actually fast with immensely lesser effort compared to Rust. There is a good chance that a highly optimised Rust version would perform even better, but at some point you gotta ask yourself how fast do you actually need it to be and is it worth it.

Thank you for the video, prime!

@Aaku13

Slick content my guy. Love it. I'm glad someone has (mostly) unbiasedly confirmed what I've seen in many years of engineering software. Go is just faster and easier to write a blazingly fast solution to a problem in. There's very few foot guns, very few things to learn, and it compiles and runs your tests BLAZINGLY fast. IMHO if a language can get you even 80% of the way to the fastest solution in ~20% of the time, then that should probably be your daily driver for latency sensitive applications.

@J-Kimble

This is actually the best case made I've heard for Go. Simpler to write, reasonable performance. I would go for it for my next project (even though I've already chosen rust for said project).

@m.minkov

Really appreciate the work you into this video! Thank you once again for making my day that much more BLAZINGLY FAST.

@GabrielAdrianSamfira

Your videos are anti anxiety medicine. Helps me unplug my brain from constant chatter and does it with really nice info. Thanks for everything!

@RobertBMenke

Would love to see if any highly experienced go/rust people would take the challenge to reimplement or refactor what you wrote while you do a video measuring the time, discussing what optimizations were made, and which language truly blazes and which one got caught up asking for feet pics on the internet.

@alexvass

Thanks

@yachint1570

I found your channel originally because of VIM but have to say that all your videos are both educational and fun to watch. Keep it up!

@dalekman8945

These videos are so much fun yet educational. And fucking hilarious thumnails to boot

@renujadecosta6408

When a comedian chooses a path in programming and becomes blazingly good at it you get ThePrimeagen.

@gustavoluchi

So fun to watch and still very informative. Keep going!

@MartinKariuki-c9k

I have read lots of comment discussions on youtube but this video has the best.:face-red-heart-shape:

@lmnts556

This was great, honestly I just like to watch programming stuff in general. It is all very interesting, the whole space is so cool. Appreciate it!

@forhadrh

That's some blazingly amazing insights! Appreciate your effort 🌸

@farzadmf

I haven't used Rust much, but I've used Go. One noticable thing that I've seen is that the compile time in Go is insanely fast, while Rust really takes its time (maybe because of the optimizations it's doing), but for a "normal" end user, I think Go is the clear winner at least in that deparatment.

And I thiink Go's concurrency is famous for a reason (as you also mentioned), and it's REALLY built-in to the language and flows with it.

Great and informative video BTW

@buzz1ebee

I do love working with typescript but go has been looking interesting for a while. If it's as easy to write and gets you free performance it I thinki might look into it. Very impressive seeing it compete against organic home grown rust.