Re:Google Go: The Good, the Bad, and the Meh
by lclarkmichalek on Monday February 11, 2013 @11:24AM
(#5201527)
That's a point I hadn't thought of. Though on the negative side, it does make it significantly harder to create a true "drop in replacement" that other languages have (i.e. where a library provides a replacement of another library without requiring any modification to the source code of an application using that library).
[ Parent
| on HN ]
Re:Google Go: The Good, the Bad, and the Meh
by chimeracoder on Monday February 11, 2013 @04:16PM
(#5203290)
You're still going to need to recompile, because Go programs are all statically linked.
Replacing the imports is pretty easy, though - because Go is so draconian about certain elements of formatting and style (including restrictions on imports), it's relatively straightforward to migrate code like this.
(The 'go fix' tool is an even better example of the power that such an opinionated compiler provides as its tradeoff)
Re:Google Go: The Good, the Bad, and the Meh
by NateDad on Monday February 11, 2013 @11:39AM
(#5201642)
That's a good thing.
Re:Google Go: The Good, the Bad, and the Meh
by lclarkmichalek on Monday February 11, 2013 @11:59AM
(#5201778)
How so? I can think of a couple of examples where libraries have needed to be replaced and it's only because their replacements were transparently compatible that the replacement was possible without major pain all around.