4 ms·

Mostly depends on how ambitious you're feeling, imo. fwiw - I learned Rust, was painful at first, but now I love it.

by brink 3y ago

swader999 3y ago
From what I've read, it seems like if you can learn Rust, go would be a quick afterthought to pick up. Just not sure if it was my own money for dev expenses if I would choose it.
- eYrKEC2 3y ago
  That is very fair. I was useless the first month of Rust. I would say that new rust devs are basically in training and unavailable for ~4 weeks. Rust mastery takes much longer than that, of course. However, the type checking in Rust is fantastic. The confidence in correctness that you have when it is complete is much higher than many other languages.
- masklinn 3y ago
  > Just not sure if it was my own money for dev expenses if I would choose it. Use case would probably be a major factor in the decision e.g. picking up rust from scratch to write a basic network service would probably be stupid unless it had very strict requirements known in advance (and even then you might want to write it in go anyway in case that works out or to quickly uncover issues you’d hadn’t predicted). If you know in advance you have very strict resource constraints however, or you really need the reliability (of extensively encoding things in the typesystem), or you’re writing native extensions (python + rust via pyo3 is great, python + go is something I’d avoid unless the entire solution already existed in Go and I could expose it to python over a pipe), etc… then the investment would likely be more worth it. Basically, how much return would you expect, Go requires very little investment, Rust a lot more.
  - swader999 3y ago
    This is a really interesting reply. I've thought of building workers in go/rust to help process the harder sidekiq jobs in our ruby solution. Kind of scared of making a Frankenstein though but yeah it might actually be the right way in some ways.

Mostly depends on how ambitious you're feeling, imo. fwiw - I learned Rust, was painful at first, but now I love it.

by brink 3y ago

Mostly depends on how ambitious you're feeling, imo. fwiw - I learned Rust, was painful at first, but now I love it.

From what I've read, it seems like if you can learn Rust, go would be a quick afterthought to pick up. Just not sure if it was my own money for dev expenses if I would choose it.

eYrKEC2 3y ago
That is very fair. I was useless the first month of Rust. I would say that new rust devs are basically in training and unavailable for ~4 weeks. Rust mastery takes much longer than that, of course. However, the type checking in Rust is fantastic. The confidence in correctness that you have when it is complete is much higher than many other languages.
masklinn 3y ago
> Just not sure if it was my own money for dev expenses if I would choose it. Use case would probably be a major factor in the decision e.g. picking up rust from scratch to write a basic network service would probably be stupid unless it had very strict requirements known in advance (and even then you might want to write it in go anyway in case that works out or to quickly uncover issues you’d hadn’t predicted). If you know in advance you have very strict resource constraints however, or you really need the reliability (of extensively encoding things in the typesystem), or you’re writing native extensions (python + rust via pyo3 is great, python + go is something I’d avoid unless the entire solution already existed in Go and I could expose it to python over a pipe), etc… then the investment would likely be more worth it. Basically, how much return would you expect, Go requires very little investment, Rust a lot more.
- swader999 3y ago
  This is a really interesting reply. I've thought of building workers in go/rust to help process the harder sidekiq jobs in our ruby solution. Kind of scared of making a Frankenstein though but yeah it might actually be the right way in some ways.