Keith Devens .com |
Thursday, December 4, 2008 | ![]() |
| ALL YOUR BASE ARE BELONG TO US. – Zero Wing | ||
|
| ← Harry Potter logistics | My Database Professor wrote Gadfly → |

Mats Henricson (http://www.henricson.se/mats) wrote:
Keith Lea wrote:
Right, but how many projects in C/C++ or C# fail? I wouldn't doubt that it was any lower.
tony (http://www.abrandao.com) wrote:
It figures, big complex bloated middleware systems, with too much hype are always a setup for dissapointment... ..want proof that simple systems lead to less failure. Look at the internet, simple protocols & apps, that do basic things and all work well and scale, Look at DNS, HTTP, HTML, SMTP, the whole world relies on these simple yet necessary codes to do the "heavy lifting" and how many of them (or the apps that commonly use them such as sendmail, apache etc) were programmed in some new fangled bloated OOP langauge, with some elaborate VM??? NONE! ,
How they arrived at 70% failure is a mystery, but when programmers have to spend more time reading the API's then coding you know something is wrong..
"Everything should be made as simple as possible, but not simpler."- Albert Einstein
Feel free to post a comment below. Please see my comment policy.
Formatting Rules (No HTML):
Generated in about 0.174s.
(Used 8 db queries)

I think the numbers are pretty vague. What does failure mean? And was it caused by Java being the implementation language, or some other reason? I mean, many projects fails (god knows I've been involved in far too many), and the implementation language haven't been the major reason in any case. Also, how many project fails in general? Maybe Java projects fare better than normal?
See, the numbers aren't that interesting without more info.