3 ms·
The Go Way ain't the traditional way. I'd argue you should want the same binary everywhere, though there's always C or you could come up with your own scheme to
by loopz 7y ago
The Go Way ain't the traditional way. I'd argue you should want the same binary everywhere, though there's always C or you could come up with your own scheme to break production.
- csande17 7y agoI don't especially care about the binary (beyond wanting it to be as small and fast as possible on end-users' machines), but I do want the behavior to be the same everywhere. In C, this is difficult because code often accidentally relies on "undefined behavior" that changes depending on the compiler and optimizations you use. But is that still an issue in newer languages that don't have as much undefined behavior? (Is this something Rust programmers struggle with, for example?)
- loopz 7y agoSafe language implementations such as Go and Rust are specifically designed to avoid such inconsistencies. If your builds differ, you never know 100% though.
- steveklabnik 7y agoRust only has undefined behavior if you use unsafe.