4 ms·

This is really cool, thanks for sharing. How do you find Rust for this code base compared to Go?

beefsack 9y ago
The main reason why I wanted to switch from Go to Rust was I was finding the type system a bit too weak for game implementations. There were even some games I was having trouble implementing at all without resorting to `interface{}` throughout the data structures. Rust has been a challenge but now that I'm fairly proficient it's very well suited to implementing the game data structures. Parsers are much more pleasant to implement in Rust too; I've written a custom parser combinator for game input and it's much easier to handle input in Rust than it is in Go.
- siscia 9y ago
  I, as well, don't love go and I prefer rust especially for the type system. I would like to hear the negative side of switching from go to rust.
  - beefsack 9y ago
    It's not that I don't like Go, it definitely has its place, but for this particular use case I found it a little painful. Personally, the things I really missed after moving to Rust are quick compile times and very high quality editor plugins. These are areas which the Rust community are putting a lot of effort into at the moment though so I'm hopeful they'll continue to improve.
- akavel 9y ago
  Would you care to write an "Experience Report" for benefit of the Go community and development future? Pretty, pretty please! The rationale and idea is described on https://blog.golang.org/toward-go2#TOC_5.3 https://blog.golang.org/toward-go2#TOC_5.3. and https://blog.golang.org/toward-go2#TOC_8 https://blog.golang.org/toward-go2#TOC_8. , with an important note to later "publish it" (i.e. just link) on https://golang.org/wiki/ExperienceReports https://golang.org/wiki/ExperienceReports. Yours seems to be an awesomely perfect case — a real-world situation, with additional case study of how a new language helps you solve the pain points!

The main reason why I wanted to switch from Go to Rust was I was finding the type system a bit too weak for game implementations. There were even some games I was having trouble implementing at all without resorting to `interface{}` throughout the data structures. Rust has been a challenge but now that I'm fairly proficient it's very well suited to implementing the game data structures. Parsers are much more pleasant to implement in Rust too; I've written a custom parser combinator for game input and it's much easier to handle input in Rust than it is in Go.

siscia 9y ago
I, as well, don't love go and I prefer rust especially for the type system. I would like to hear the negative side of switching from go to rust.
- beefsack 9y ago
  It's not that I don't like Go, it definitely has its place, but for this particular use case I found it a little painful. Personally, the things I really missed after moving to Rust are quick compile times and very high quality editor plugins. These are areas which the Rust community are putting a lot of effort into at the moment though so I'm hopeful they'll continue to improve.
akavel 9y ago
Would you care to write an "Experience Report" for benefit of the Go community and development future? Pretty, pretty please! The rationale and idea is described on https://blog.golang.org/toward-go2#TOC_5.3 https://blog.golang.org/toward-go2#TOC_5.3. and https://blog.golang.org/toward-go2#TOC_8 https://blog.golang.org/toward-go2#TOC_8. , with an important note to later "publish it" (i.e. just link) on https://golang.org/wiki/ExperienceReports https://golang.org/wiki/ExperienceReports. Yours seems to be an awesomely perfect case — a real-world situation, with additional case study of how a new language helps you solve the pain points!