News for hackers. Stuff that matters.
Re:9 Hole Code Golf Challenge by TylerE on Sunday December 29, 2013 @11:15PM (#6983008)
Why? That's a near useless-metric on any device with more than 32kb of ram, and highly variant on things like compiler and library minor versions.
Re:9 Hole Code Golf Challenge by userbinator on Sunday December 29, 2013 @11:53PM (#6983096)
In a time when computation is largely constrained by memory bandwidth, the size optimisation can have quite practical benefits. There will definitely be variance on different systems but this is why you standardise on the system for a competition.

Also, I think it's not quite so impressive to see a 100-byte source file turn into a few hundred KB or few MB binary as it is to see what could be done in a 64K, 4K, or even 256 bytes binary.

Re:9 Hole Code Golf Challenge by TylerE on Monday December 30, 2013 @12:15AM (#6983150)
Modern processors commonly have 8MB of L2 and 16MB or even more of L3 cache. Shaving 10kb off a binary is meaningless.
Re:9 Hole Code Golf Challenge by aeykie on Monday December 30, 2013 @02:17AM (#6983506)
Modern hard drives have gigabytes of storage, so shaving 100 characters of a source code is pointless. I always thought code golf was for fun more than anything.
Re:9 Hole Code Golf Challenge by userbinator on Thursday January 02, 2014 @09:34AM (#6999703)
...shared among all the processes in the system. Having 8MB of cache to yourself may seem like a lot, but share it equally with 100 others and you're left with ~80KB.