Re: Why we need computers calling balls and strikes
I'm not against the technology. But I've done enough large scale systems integration and computer software projects to know there are an *awful* lot of things to work out to put a system like this into live play. And a gazillion things can (and do) go wrong and need to be worked out.
It's one thing to say that "oh, they have it all now, it will all work perfectly" and then take a *really* close look at it (because baseball wonks like us will) and work out the technical minutiae of everything that's done.
If MLB is serious about it, put it in place in a pilot down in single A ball where the mistakes won't be magnified. Work out all the kinks, fixes mistakes, work out issues, and take a season to get it right and prove it out. Because from what I've read in here, umps are right 92-95% of the time and the current technology is right 97% of the time. This is a *huge* change in the game for that extra 3% and you damn well get it right the first time out in a MLB park. Because if you don't, you'll get crucified over it. My favorite saying when asked about a project is "anything is possible with time and money". So put some time and money in at it.
Pay attention to the open sky