News for hackers. Stuff that matters.
Re:Porting a NES Emulator from Go to Nim by loudmax on Friday May 01, 2015 @04:29PM (#9474309)
If the Nim binary is dynamically linked, comparing the size to a Go binary isn't always valid. There are reasonable trade-offs to consider when selecting dynamic vs static linking. Admittedly, when you're running an NES emulator on your desktop probably isn't one of them, you're not likely to care either way.

The Nim -> C -> emscripten path is very impressive. Kudos.

Re:Porting a NES Emulator from Go to Nim by ploxiln on Friday May 01, 2015 @05:32PM (#9474657)
Go also dynamically links glibc by default on linux, for the domain name resolver functions.

I'm not sure what Go does on OS X, but I know that it's not possible to statically link the c library on OS X.

Re:Porting a NES Emulator from Go to Nim by sunnyps on Saturday May 02, 2015 @02:12AM (#9476078)
I thought gc only statically links and it was gccgo that had the ability to dynamically link.
Re:Porting a NES Emulator from Go to Nim by ploxiln on Sunday May 03, 2015 @04:53AM (#9480542)
gc only statically links to compiled go objects, and (may have changed recently? or soon?) only dynamically links to c libraries (via cgo).