At 01:18 06/01/2015 -0800, Michael Crawford wrote:
If user error can lead to a crash, that crash is ultimately the
fault of the software developer.
No. If a user powers down a system without closing down properly,
that is not the fault of the software. If a user is impatient and
kills a running process, that is not the fault of the software.
If the problem is a bad memory module, then the fault lies with the
electrical engineer who designed it, or with the manufacturer.
So *not* the software developer, then.
The user would only be to blame if he handled or installed the
memory improperly, say by not observing antistatic procedure.
So that wouldn't be down to the software developer, then?
Or processor overheating.
Then the fault would lie with the engineer who designed the
computer, unless the user blocked the ventilation holes.
So (in either case) not with the software developer, then?
Or disk corruption.
That's likely the fault of the software developer who wrote the
filesystem code.
So *not* the software developer (of the application software) that we
are talking about.
Or (Windows) registry corruption.
That's Microsoft's fault for making such a critical system component
so vulnerable to corruption.
So *not* the application software developer?
Or malware.
The vulnerability of Windows to malware is largely Microsoft's fault.
So *not* the application software developer, then?
Your claim (to which I responded) was "If an end-user application
crashes during normal use, it is ultimately the fault of *its*
software developer" (my emphasis) - in other words, that if
OpenOffice crashes it can only be down to the developer of
OpenOffice. That's simply untrue - and I'm glad to see you agree with
me so comprehensively.
Brian Barker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org
