1,306 karma · joined July 9, 2011
Apple learned it the hard way.
I thus consider all dogfooding unethical that is not done by somebody who has, or is provided with, a lot of influence on the product.
Talking of morning exercises, Marcus Aurelius used to remind himself in the morning that he would be around exactly the kind of people you describe, but that they did not have the power to make him crazy if he is aware of their inevitability: http://classics.mit.edu/Antoninus/meditations.2.two.html (BTW: I only used this source because it seems to be public domain and available online, if you want to read translations of ancient texts, invest in a modern one that is more convenient to read.)
(1) Of course, if you start your own company, you will be dealing with things you can't control as well.
Edit: Replaced asterisks that made the text italics.
Of course you realize even bigger gains on many common workloads using parallelism, but this part of his argument doesn't need the first part, which was wrong.
The first part of this statement is plain wrong. Single thread performance has improved a lot due to better CPU architecture. Look at http://www.cpubenchmark.net/singleThread.html and compare CPUs with the same clock rate, where a 2.5 GHz. An April 2012 Intel Core i7-3770T scores 1971 points while a July 2008 Intel Core2 Duo T9400 scores 1005 points. This is almost double the score in less than four years. Of course, one factor is the larger cache that the quad core has, but this refutes Armstrong's point that the multicore age is bad for single thread performance even more.
For exposure to a more balanced point of view, I would highly recommend Martin Thompson's blog mechanical-sympathy.blogspot.com. It is a good a starting point on how far single threaded programs can be pushed and where multi-threading can even be detrimental.
Also, I think that fault tolerance is where Erlang really shines. More than a decade after OTP, projects like Akka and Hysterix are finally venturing in the right direction.