Now I am debating between Rust and Go for backend development (for a web service). Which one between these two would be recommended for my needs? My priorities are to be able to learn quickly and develop/iterate as fast as possible.
For a web service with fast iteration times, I'd probably pick Go of those two. While I'm not personally a giant fan, I think it is a much simpler stack that lets developers be pretty productive especially in the domain of web services.
If that was the case, wouldn’t people who love Go have created one after more than a decade in existence?
The reason why Go developers don’t like “frameworks” a-là Ruby on Rails in the Ruby ecosystem is because the Go community generally prefers libraries over frameworks because Go’s simplicity and flexibility allow developers to compose their solutions using small, composable packages rather than being constrained by a rigid framework.
This approach often results in more efficient and maintainable code. The Go philosophy emphasizes minimalism and encourages developers to avoid unnecessary abstractions.
https://github.com/mingrammer/go-web-framework-stars?tab=rea...
But you won't find anything that's anywhere near as comprehensive and batteries-included as Rails or Django.