A week ago I was asked to fix a problematic webapp suffering from memory leaks. How hard can it be, I thought – considering that I have both seen and fixed hundreds of leaks over the past two years or so. But this one proved to be a challenge. 12 hours later I had discovered no less than five leaks in the application.
-
Why Companies Should Love Their Data Unequivocally
-
Lions, and Tigers, and OP Codes, OH MY! – Hacking Java Bytecode for Programmers (Part2)
-
Apache Drill: Interactive Query and Analysis
-
Google's open video proposal closes door on software freedom
-
The Multicast Revival: LAN Multicast with Code Example
-
What’s New in Node.js and libuv this Week – May 17, 2013 - Debugger, Load Balancing and Crypto Performance
Add your comment
