3 ms·

I hope they focus more on their Go client than the C++ one. Something like this needs to be as secure as it can get. No reason to have it vulnerable to memory l

I hope they focus more on their Go client than the C++ one. Something like this needs to be as secure as it can get. No reason to have it vulnerable to memory leaks and such, if they don't have to.

ixmatus 13y ago
If that's your reason for trusting an implementation in Go over C++ then I would say they should level up and use Haskell. Or even better, Agda. There's also ATS but I think the community around Haskell and Agda is more populous. A garbage collected language is an improvement over possible memory leaks due to human responsible memory allocation, but I think a larger problem is most programmer's (very human) inability to separate pure from impure code. Languages with very strong type guarantees do it for you and give you the tools to protect yourself from a lot of problems that are common in any language from Assembly all the way through to Go (I think Rust is actually well suited as well since it has a better type system than Go, but I haven't used the language so I can't speak to that). [EDIT] minor edits.
- mrec 13y ago
  The Rust folk tend to avoid talking in terms of purity nowadays. Graydon had a good writeup of the pitfalls: http://thread.gmane.org/gmane.comp.lang.rust.devel/3674/focus=3855 http://thread.gmane.org/gmane.comp.lang.rust.devel/3674/focu...