As an engineer, I'd like to point out that most of you are making a mistake about drive by wire throttles. You're actually complaining about the complex system the drive by wire throttle is wired into.
A drive by wire throttle does not need to be wired into the computer. It can be rigged as a dedicated stand alone system consisting of nothing but the input potentiometer (pedal) and the actuator (throttle plate). Done this way, it will act just like a mechanical throttle linkage or cable. And if it fails, it will fail just like a mechanical throttle would. And you would use a conventional throttle return spring. And all would be perfectly happy with it. Think pertronix for throttles if you will.
But that is not what is done. Instead, it's wired into a complex computer, taking multiple other inputs, processing it, and then the computer comes up with some sort of answer that it sends to the throttle.
THAT is where the problem lies. The complexity of the system. That computer can come up with some serious goofy answers to give the throttle plate. Some that are terrible for performance (elimination of power braking for example), some that are just plain dangerous (holding the throttle open).
A whole lot depends on the coding. How buggy is it, how robust, how complex. A good bit depends on the quality of the parts, and what happens when those parts fail. Lots of unforseen problems arise here, and are darn hard to isolate.
It would be convenient to blame it all on the engineers at this point. And a good bit of it can rightly be blamed on the engineers. But other folk contribute to the problem. Bean counters who want to use cheap parts and cut testing short. Marketing folk who want the product out now, before all the bugs are worked out. Lawyers who want liability protection for the company, etc. These things all contribute to product that is overly complex, ever increasingly complex, and riddled with problems. In this case, a car with drive by wire throttle, but we could just as easily be talking about a toaster.
Is it all therefore bad? No. Look at the incredible power coming out of modern race car engines using very complex computer codes and zillions of inputs. It can work great! So what's the difference? Market, focus, resources, etc. The Honda F1 racing team is focusing on a handfull of cars, with the single objective of going fast, and all resources are dedicated to this one task. This team has a much better chance of making a better product than the vast Honda auto group. That group is split up into many cars with all kinds of different objectives. From cup holder locations to headliners, and "oh yea", throttle control. This bunch is far more likely to run into trouble because they are not as focused as the racing team.