<br><br><div class="gmail_quote">On Thu, Jul 16, 2009 at 4:09 PM, Michael Mol <span dir="ltr"><<a href="mailto:mikemol@gmail.com">mikemol@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Jul 16, 2009 at 4:00 PM, Adam Tauno<br>
Williams<<a href="mailto:awilliam@whitemice.org">awilliam@whitemice.org</a>> wrote:<br>
>>Garbage Collection. In managed platforms like .NET and Java, it's very important to understand if you want to get any kind of performance out of a "large" application.<br>
><br>
> It matters in 'unmanaged' environments like Objective-C and Python as well (and in PHP, Perl, etc...). Most of these use reference counting to auto release old objects. But reference counting can fail in interesting ways, even assuming there are no bugs in the implementation. Maybe these are 'quasi-managed' enviroments?<br>
><br>
> And unmanged C, etc... has GC problems as well - where the GC is the programmer. :)<br>
<br>
It all comes down to being aware of what goes on under the hood. :)<br>
<div><div></div><div class="h5"> </div></div></blockquote><div>Or getting more memory. There's a performance<br>cost to all the monitoring, and while things like<br>swapping work, as soon as you do things slow<br>down a lot. You can't program your way out of<br>
hardware limitations for long, if that's the situation<br>you have.<br><br>The Russians used to be very good at writing <br>very tight code, because their computers sucked.<br>For much of the world the most economic way to<br>
make a program run faster can be to simply get<br>a faster computer.<br><br>And more memory.<br><br> --Bob<br><br></div></div><br>