![]() |
Quote:
|
Quote:
Duenez has a small chance of sticking in LF, but most think he's 1B only. |
Quote:
|
Quote:
|
<blockquote class="twitter-tweet" lang="en"><p>That last RT is just a spectacular display of wrong. Too many jokes to choose just one, but Yost really wants to bat MLB's worst hitter 2nd.</p>— Sam Mellinger (@mellinger) <a href="https://twitter.com/mellinger/statuses/449666235689472000">March 28, 2014</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> <blockquote class="twitter-tweet" lang="en"><p>If you or someone you know loves Ned Yost, talk some sense into him. I know the Royals watch this account. Someone help him.</p>— Sam Mellinger (@mellinger) <a href="https://twitter.com/mellinger/statuses/449666452455321600">March 28, 2014</a></blockquote> <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> |
Quote:
|
I think I've written 100 posts pushing back against lineup overreactions. The order for #2-#5 or #3-#6 shouldn't matter, but this is too much.
You put your bad hitters #8 and #9 for one simple reason: you don't want them to bat more often than they have to. Putting your #9 at #2 is stupid unless he's some OBP freak with infield dirt power (which isn't Escobar), and even then its very questionable. |
Is a spring training lineup where the projected #2 hitter is injured such a big deal?
|
Quote:
Infante is in Arizona, and Yost is bumping Escobar up to #2 to replace him. Obviously what he should do is bat Gordon 2nd when Infante is not playing, but Escobar should be safely at the bottom if Infante is healthy. |
Quote:
|
Quote:
|
Quote:
So, if Infante is healthy (knock on wood), then we have nothing to worry about, but batting Escobar 2nd if Infante is not available is so stupid, it warrants a big twitter reaction. If nothing else, we now have another reason to care a lot about Infante's elbow. |
Escobar should never bat higher than 9th
|
No sense at all to this.
|
Quote:
|
All times are GMT -6. The time now is 04:02 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.