• POLL: Should I commit to Rust or Go? I can't decide. ······················ • · · · Results · · · · [1] 15% • Rust (2 votes) · · [2] 62% • Go (8 votes) · · [3] 23% • Just forget it and stick with what you already know. (3 votes) · · · • ··········································································· •
2 years ago · 👍 martin, techpriest
@warpengineer: I hear you. Carp just seems like an interesting project. Its a "lisp" with a memory management system similar to rust(or maybe I am wrong?), static typing etc.. Enjoy learning whatever language you choose! · 2 years ago
@warpengineer I would say then, go for the one that allows you to do things you couldn't do before :) Rust and C fulfil the same type of tasks, so I would go for Go ]2] then. · 2 years ago
@threkk nothing specific. I'm always looking for the next thing to learn. · 2 years ago
I guess the question first is... what do you want to do? · 2 years ago
@piero I just looked at Carp. I think I've had my fill of Lisps over the years though. Maybe in the future. · 2 years ago
I had the same question. I know Rust is "omg fast and safe and optimal" but I went to learn Go [2] I also love C. · 2 years ago
Go floating to the top (and rust sinking to the bottom) fills my heart with joy! :) · 2 years ago
Maybe give Carp a look? · 2 years ago
@sub I come from a decades long C background and I thought Go was much more C-like than Rust. It makes me feel more at home. I understand wanting to stay but I like to learn new languages. · 2 years ago
[2] · 2 years ago
[3] · 2 years ago
I tried Rust and all of the rules made me want to kill myself. I also don't like the way Go enforces a particular coding style. I went back to good old plain C and couldn't be happier. · 2 years ago
Thank you everyone. I was originally leaning towards Go but then read about Rust in the Linux kernel. Then even MS said they're putting Rust in the Windows kernel. So I had doubts. Your inputs and the article shared by @martin were very helpful. I'm going for Go! · 2 years ago
[2] Had great success with Go in multiple projects and teams (including teams without Go experience and senior developers), it's a simple language that makes collaboration easy, productivity is good, it's stable (no disruptive changes to the language/tools) and performance is good enough for many things. It's my go-to language for servers. · 2 years ago
[2] I tried both and had fun with each. ultimately Go was more practical and I ended up actually finishing projects with it. · 2 years ago
I'd say it depends entirely on your main domain that you're developing for. Systems stuff I'd go Rust (only until Zig has matured) if you're mainly doing network stuff I think you'd be alot more productive in Go. · 2 years ago
I happened to read a good post about this very subject recently, by the way: https://bitfieldconsulting.com/golang/rust-vs-go · 2 years ago
https://bitfieldconsulting.com/golang/rust-vs-go
[3] · 2 years ago
[3] · 2 years ago
[2] · 2 years ago
I'd use [1] Rust. It's complex, yes. But golang forces your coding style which I hate. And generats a huge binary. it's like it's running on it's own OS. · 2 years ago
jOiN uS! [1] We ArE lEgIoN. cOmE tO RuSt!!
In all seriousness, I'm a big fan of Rust. But honestly you should go with what works best for you. · 2 years ago
I prefer Go [2] for its simplicity, but I think it also depends on what you're planning on doing with it. If I were writing a core system utility type thing for example I'd probably pick Rust. · 2 years ago
I'm a bigger fan of the simplicity of Go than the better features + complexity of Rust, so I'd go [2] · 2 years ago
[2] · 2 years ago