We always build software to be easily ported, machine independent, and easy to maintain and enhance. These are things much to be desired and unqualifiedly good, as long as there is no cost to the user . If ease of development or support imposes a performance, convenience, or learning cost upon the customer, this must be looked at as a tradeoff, not decided preemptively in favour of the developer. It fills three discs. You have to read about three pages of manual to get started on it, and it contains hundreds of pages of intelligent, useful, and witty on-line assistance.
All response is absolutely instantaneous.
No error is fatal. You can always back up. This is one of the assumptions we should question. I don't have the answers to these questions. But I think we have to consider them.