On a scale from 0 to 1

How based are your arrays?

>>49
In my experience, only imperative programs even attempt to recover from errors. All out of memory and other errors violate ``referential transparency''. The common solution of functional programmers is to pretend these errors don't exist.

"80% of code is error handling"

If the code is used in a situation where a lot of things can go wrong, you want that much error handling. No amount of type checking or formal verification would prevent a hardware error. Sometimes you have multiple processors running the same code in case of an error.

imperative requirements of explicitly managing things in exact order.

As expected, you don't know anything about imperative programming.

Now you see why FP shills wanted C to become popular.

We went to lunch afterward, and I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"

They can't compete with proper error handling, but they can attempt to compete with C and Unix.