DEV Community

Discussion on: Rust or Go for web development?

Collapse
 
therealkevinard profile image
Kevin Ard

I was in the same scenario some time ago. Rust was much younger - a blip on the radar, actually - and I dug into Go. I can't advise one way or the other, but I can chime in from the "person who chose Go" side.

If I was going to sum it up: Go really doesn't leave much to be desired. It ha some rough edges (looking at you package management), but at the end of the day... I'm a little sad if I was using something else.

Whenever rust vs go comes up, invariably someone says go's strength is in its high velocity. I can attest to that. I have a number of commit messages that read make the compiler happy, but not too bad. And, eventually it clicks - that was my fault lol.

DX is solid. IDEs like strict typing of course, but the compiler speed is a monster. In dev, it feels more like an interpreter than a compiler. It's a little confounding that delve JUST NOW got the ability to run a method call during step-debug, hut cest la vie.

If you're coming from front-end, I assume you're comfortable with Node.

  1. You will miss package.json like crazy (go mod is standard now, but it's still not quite... There)

  2. You will love how smooth async is (huge plus if you work with rest)

  3. You will be angry at unmarshaling an (uncertain) api response

  4. You will be completely freaked out when the call stack takes you down into the RAM chip.


That's what I have. Now I spy on this thread. ... because I still search "go vs rust" at least once a week 🤷‍♀️

Collapse
 
selengora profile image
Selen Gora

Hello :)
Thank you for comment! I really loved your list about love/hate. It's good to know the problems I'm going to encounter in advance :)