Hacker News new | past | comments | ask | show | jobs | submit login

I've used Go and Rust for network services, and they honestly feel completely on par with one another from a DX and ergonomics perspective. I wouldn't be surprised if Rust starts eating into Go marketshare for microservices.

There are some Googlers angling for this.




I love Rust, but Go is a much much simpler language, especially for network services. For example, the experience of goroutines vs rust async is night and day in terms of complexity. Also, the borrow-checker introduces a lot more ceremony when managing network peer entities, particularly structuring relationships between entities - a very common requirement in network applications.

Not that I'm against Rust for network services, but with Rust you're accepting increased complexity for increased safety - a worthwhile tradeoff depending on the project.


I can't agree they're on par based on function coloring and slow compile times alone.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: