Why don't we take another approach to the unrealistic $30B estimate? Low quality software (aka win32) causes eventual crashes, wiping out some work. This is a very superficial estimate, but the estimate presented in the article is *also* very superficial. Suppose there are 100 M windows users around the globe. Suppose every day 1% experiences some kind of serious data loss. 1 M users. Suppose every user who experienced data loss, lost an average of 2 hours of work. We have 2 M hours of lost work everyday. If every worked hour costs an average of $20, we have a $40 M loss everyday, due to the instable nature of win32 products. The total estimated loss is $14.5 B/year. What do you think?
Slashdot Mirror
Why don't we take another approach to the
unrealistic $30B estimate?
Low quality software (aka win32) causes eventual
crashes, wiping out some work.
This is a very superficial estimate, but the
estimate presented in the article is *also*
very superficial.
Suppose there are 100 M windows users around the
globe.
Suppose every day 1% experiences some kind of
serious data loss. 1 M users.
Suppose every user who experienced data loss, lost
an average of 2 hours of work.
We have 2 M hours of lost work everyday.
If every worked hour costs an average of $20, we
have a $40 M loss everyday, due to the instable nature of win32 products.
The total estimated loss is $14.5 B/year.
What do you think?
Petabytes being processed ... 5 864.html
Is Echelon alive?
http://www.wired.com/news/news/politics/story/1