4 ms·
Disclaimer: I am neither proficient in Rust nor Golang - rather a hobbyist using them in non-professional contexts. I have a bit more programming experience wit
by vibesngrooves 6y ago
Disclaimer: I am neither proficient in Rust nor Golang - rather a hobbyist using them in non-professional contexts. I have a bit more programming experience with Golang than Rust (just finished the Rust book).
I think you should identify which ecosystem and toolset you like working with. I'm leaning towards Golang for web development and web/system protocols. I chose to explore Rust as an intro to embedded development and audio/dsp programming - an alternative to learning C++. Rust seems great as a well-absracted, yet powerful and performant low-level programming language. I feel much more comfortable writing code with the Golang toolchain, but I feel much more confident with my end-result thanks to the strictness of the Rust compiler. I appreciate the specifics Golang conventions and opinions as well as the openness/comprehensiveness of the Rust language and community - not saying there aren't conventions and idioms, rather there are so many options and approaches to implementation within the language. YMMV, figure out what feels more natural to your process, style, and application context.
- poletopole 6y agoThanks for answering. I probably see myself concluding the same. I asked IH the same question and I ended up concluding that in my case where I'll be doing lower level programming for the WASM, the end users would probably benefit more if they used Golang. Using both is definitely an option, I'm just too unfamiliar with either language to have known the right call. I just wish Golang 2 would move a little faster, but I don't blame the community for being prudent.