Galarraga's Perfect Game


Recommended Posts

Everybody makes mistakes, even umpires.

Its so easy for people to villainize the decisions that other people make, especially from the outside.

I think Joyce feels bad enough as it is, without the many boos and threats I'm sure he is going to receive from fanatics.

Maybe actions like these will cause changes to happen, like instant replay.

Either way, I don't know whether i feel worse for Galarraga or for the nonsense Joyce will have to deal with.

Even Leiland was quick to point out how good of an umpire Joyce is. The guy made a bad call at the worst possible time and has already admitted his mistake. It really sucked to watch it as it happened, but once emotions calm down, you can feel bad for Joyce, too.

Nah, **** Joyce.

He's supposed to be a veteran. He knew a perfect game was on the line.

1. It was not a close call at all.

2. If it were a close call, you give the benefit of the doubt to the pitcher.

The only good thing out of this is that instant replay will be used for every game now (hopefully), but nothing compares to poor Galarraga's stolen perfect game.

No matter how much Joyce apologizes, what is done cannot be undone. So with that said, **** Jim Joyce.

Instant replay is likely not going to be used because of this one incident. Do you remember how many calls were blown in the 2009 postseason? One game during the regular season will not change it. While Joyce blowing the call sucks huge balls, it's going to happen. Should we institute replay to make sure everything in basketball and other sports is correct? No, it wouldn't be practical. It would drag on the game for hours. Selig won't allow this to happen on his watch. Baseball fans are lucky to have the limited replay that they have.

Nah, **** Joyce.

He's supposed to be a veteran. He knew a perfect game was on the line.

1. It was not a close call at all.

2. If it were a close call, you give the benefit of the doubt to the pitcher.

The only good thing out of this is that instant replay will be used for every game now (hopefully), but nothing compares to poor Galarraga's stolen perfect game.

No matter how much Joyce apologizes, what is done cannot be undone. So with that said, **** Jim Joyce.

Even Jim Leiland said he had no idea what the correct call was before seeing the replay. The reason? Umps listen for the sound of the ball hitting the glove and feet hitting the bag. The ball was snow coned, so it never made a sound and, thus, would appear to get to Galaraga later than it did. Also, close calls at first go to the runner. That's the rule, not vice versa.

On top of that, you can question Detroit's defense. They had Cabrera playing much further off the base than a normal infield setup. If he had been playing a normal distance from the bag, there's a good chance he would have been able to cover first and the 2nd baseman could have fielded it.

Even Jim Leiland said he had no idea what the correct call was before seeing the replay. The reason? Umps listen for the sound of the ball hitting the glove and feet hitting the bag. The ball was snow coned, so it never made a sound and, thus, would appear to get to Galaraga later than it did. Also, close calls at first go to the runner. That's the rule, not vice versa.

On top of that, you can question Detroit's defense. They had Cabrera playing much further off the base than a normal infield setup. If he had been playing a normal distance from the bag, there's a good chance he would have been able to cover first and the 2nd baseman could have fielded it.

Umps have their eyes too. On the previous play he should have noted that the ball did not make a sound.

Now, I know rules say one thing, but we all know that umps do whatever they want (like calling this runner safe when he was clearly an out). And in a situation like this, a perfect freaking game, you give the benefit of the doubt to the pitcher.

If umps go only by the sound of the ball and the runner stepping on the base, then hire legally blind umps so there is nothing to argue about.

You can argue how Detroit's defense was positioned, but even so the runner was an out by a step.

So I still say that Joyce can go **** himself. Sadly the Commissioner is a ***** and won't do right on this situation.

And not to mention all the other bad calls umps have done this season. There is a desperate need of young talent among umpires because these old meat bags don't have good reflexes anymore.

I feel absolutely sick for Galarraga. He is an absolute professional and reacted as such, but he has got to be heartbroken now that he has had a little time to think about it. This is a once in a lifetime opportunity that has only been accomplished like 20 times in about 120 years. It's what every pitcher dreams about in their career but the select few are able to accomplish. For Galarraga to be robbed of this by such a horrible call on such a crucial play is a travesty.

You are being way too emotional about this to warrant much more debate, but bad calls happen and this one happened at a really bad time. Look back to '96 and Jeter's homerun that really wasn't (I'm a Yankee fan, btw).

As for your argument about it being a perfect game and the benefit of the doubt, you can't change the rule like that. You can argue about umps doing whatever they want, but they actually don't. They have rules of the game to follow and the rule, technically, says that a tie goes to the runner; perfect game or not. You can't change the rules based on the context.

As for your argument about it being a perfect game and the benefit of the doubt, you can't change the rule like that. You can argue about umps doing whatever they want, but they actually don't. They have rules of the game to follow and the rule, technically, says that a tie goes to the runner; perfect game or not. You can't change the rules based on the context.

If they call non-home runs home runs, if they call pitches that are clearly balls strikes, if they call runners that are clearly out safe... umpires do whatever they want.

Of course I'm emotional about this. Its a perfect game, its only been done 20 times in the history of baseball.

I wouldn't be so ****ed off if it were a close call, but even fans from Cleveland knew the runner was out. Even the runner knew he was out.

Those aren't examples of umps doing whatever they want. Those instances are clear cut cases of human error. Just like a pitcher will never finish a complete season with a 0.00 ERA or a position player with a 1.000 AVG, so goes umpiring. People make mistakes.

On top of that, you can question Detroit's defense. They had Cabrera playing much further off the base than a normal infield setup. If he had been playing a normal distance from the bag, there's a good chance he would have been able to cover first and the 2nd baseman could have fielded it.

The 2B should have gone after that, Cabrera could have cost them the perfect game in what he did.

Also, is no one up in arms about how a blown call last night cost the Twins an extra innings against the Mariners?

Where is the reaction to that?

You are being way too emotional about this to warrant much more debate, but bad calls happen and this one happened at a really bad time. Look back to '96 and Jeter's homerun that really wasn't (I'm a Yankee fan, btw).

As for your argument about it being a perfect game and the benefit of the doubt, you can't change the rule like that. You can argue about umps doing whatever they want, but they actually don't. They have rules of the game to follow and the rule, technically, says that a tie goes to the runner; perfect game or not. You can't change the rules based on the context.

There is no rule that states that a tie goes to the runner.

But that's how it ALWAYS goes. Seriously, if the Ump think it's a tie, it will always be awarded to the runner. Context doesn't belong in the decision.

No it doesn't ALWAYS go that way. An umpire does not stand out there and think "Oh that looked like a "tie"" and call the runner Safe. A "tie" is just not possible to see. I've been umpiring everything from Little League to college ball for 20 years and I've always been taught unless the runner beats the ball, call an Out. And I guarantee you that the MLB guys have been trained the same way.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop 'Google Chrome' is downloading without you agreeing to it. Fun right? Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!