<story><title>So We&apos;ve Got a Memory Leak</title><url>https://stevenharman.net/so-we-have-a-memory-leak</url></story><parent_chain></parent_chain><comment><author>smallstepforman</author><text>I just dont understand the fear with manual memory management. With RAII and and simple diligance (clear ownership rules), managing memory is an easy engineering task. I actually find it *more* challenging to deal with frameworks that insist or reference counting and shared pointers since ownership is now obscure.&lt;p&gt;I create it, I free it. I transfer, I no longer care. Its part of engineering discipline. Memory bugs are no worse than logic bugs, we fix the logic bugs, makes sense to fix the memory bugs. Disclaimer: I do embedded complex systems that run 24&amp;#x2F;7.&lt;p&gt;We do the same for OS resources (handles, sockets, etc) and dont use automatic resource managers, we do it manually. So why complicate the design with automatic memory management?</text></comment>
<story><title>So We&apos;ve Got a Memory Leak</title><url>https://stevenharman.net/so-we-have-a-memory-leak</url></story><parent_chain></parent_chain><comment><author>DonHopkins</author><text>&amp;quot;I&amp;#x27;m not a real programmer. I throw together things until it works then I move on. The real programmers will say &amp;#x27;Yeah it works but you&amp;#x27;re leaking memory everywhere. Perhaps we should fix that.&amp;#x27; I’ll just restart Apache every 10 requests.&amp;quot; -Rasmus Lerdorf, PHP Non-Designer&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikiquote.org&amp;#x2F;wiki&amp;#x2F;Rasmus_Lerdorf&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikiquote.org&amp;#x2F;wiki&amp;#x2F;Rasmus_Lerdorf&lt;/a&gt;</text></comment>