memory leak? big deal
Aside from a segfault, this is about as big of a deal as it gets.
- the bad focus: if you focus on the code quality or on Agile methods, you lose the goal which is to code faster. We have such a focus on code quality that any simple task requires days to code. It's ridiculous.
Strange, I thought the goal was to break things to small, manageable tasks. If any simple task requires days to code, regardless of the level of code quality, then your tasks are too large. I follow Cockburn's approach to development: the use case breaks the problem down into very small chunks that I can then implement. In regards to project timelines and code quality: Using shortcuts and hacks may get the initial part of the project moving along, but it will come to bite you later on when there are additional requirements and bugs.
Everything these days seems to be obsession with Free Free Free because there's some expection that selling advertising space is the best way to construct a stable world wide web.
I don't think the main concern is a stable web. The concern for most companies is how to generate profit. Plenty of companies have proved that providing free content with advertisements is a viable business model. I don't think many rational people are arguing it works for every facet of business on the internet though. The competition in the marketplace is main force that is driving these services to be free. If a service like Twitter started charging, another company would quickly offer the same service for free. As a consumer, I like this. I don't really care if someone cannot figure out a way to make money off of Twitter. I want the most benefit for the least cost. Getting the most benefit does not always mean free though. I choose to pay Google to provide their email client for a small business. There are plenty of free email clients, but I think GMail is worth the cost. When the services you mention start giving some sort of benefit over the competition, then they can start charging consumers.
Thus spake the master programmer: "When a program is being tested, it is too late to make design changes." -- Geoffrey James, "The Tao of Programming"