News for hackers. Stuff that matters.
Re:Taking C Seriously by mbq on Wednesday November 02, 2011 @07:13PM (#3189361)
Zawinski's point is true iff "large application" means an application which allocates and frees plethora of tiny chunks -- however I will argue that this is not a necessity, rather a style coming from a try to port scripting experience to lower-level languages to speed up development. Probably in most cases this is not a problem (no one will notice 100us speedup in GUI), but if one starts to tweak GC or new to rescue efficiency or argue which is better, it is certainly better idea just to write it in C, with all those ugly buffers and pointers. If you already have to track memory use in your mind, why not to just take control of it?
Re:Taking C Seriously by drfugly on Thursday November 03, 2011 @12:50AM (#3190347)
Because then you have to control ALL of the memory, not just the data that you're interested in optimizing. Not to mention that (at least in the JVM) the gc is pretty tweakable, and the entire team may not need to know about all of the tweaks.
Re:Taking C Seriously by mbq on Thursday November 03, 2011 @05:52AM (#3191013)
This is precisely how it looks from this "microallocating" perspective.