You should have done at least a full project in both, a bit more than just scratching the surface.<p>I find opinions from people who only know one side not very useful, because they're usually judging on how they are imagining things to be, rather than how they would see things after giving it a serious chance.<p>Talking to an expert who knows both sides well is usually more nuanced.<p>I hope that makes sense. If this gives good responses, I would like to ask the same question about other polarizing technologies and paradigms. Like dynamic vs static typing for example.
For me golang vibes are better.<p>Go is a little too verbose but in a stupid way. Rust is too verbose in a clever way. Go is so dumb it is mind numbingly boring. Rust is so clever it becomes boring to learn.<p>You can use go in about 1 way that works. Rust you can use in many different ways. My guess is that really knowing rust is 2-5x harder than really knowing go.<p>To really get into go you need to understand the runtime, scheduling and especially GC. For rust you need to at least understand the compiler the macro language and of course the borrow checker. Then if you want to do concurrency you need to look into async await or whatever is going on these days.<p>For whatever reason I find the go runtime fun to learn about and the rust compiler tedious to learn about.<p>Go tools are smoother and easier to learn. I know it makes me a philistine but fast compile times are nice.