Re:Go reliability and durability at Dropbox
by didibus on Friday August 04, 2017 @01:38AM
(#14926564)
Easier to go from python to go than to rust.
[ Parent
| on HN ]
Re:Go reliability and durability at Dropbox
by Dowwie on Friday August 04, 2017 @05:56AM
(#14927496)
How so? You can extend Python with Rust but you can't with Go. Go requires a complete rewrite or independent service.
You can write go with the same loose nature of Python. Conceptually you can write programs the same and get some speed boost + type checking while you're at it.
It's like a more intense form of adding annotations in theory.
So while it requires a rewrite, a cost which you should not write off either, it can feel similar to Python but more verbose. Where Rust feels like Haskell and C++ had a child together and can be more jarring to switch to (in my experience as primarily Python/Django who uses Go in many side projects and tried Rust up-to and around 1.0).
Re:Go reliability and durability at Dropbox
by Dowwie on Saturday August 05, 2017 @06:35AM
(#14935101)
Thanks for commenting. I think I took the statement too literally. If I understand you correctly, the transition from Python to Go is easier because learning/using Go requires less cognitive overhead than what is required of Python to Rust.