BubbaTough wrote:There are clearly positions where promotion to rook is the best move, but unlike promotion to knight, they do not occur frequently enough in real games to be an elo contributor (or even elo neutral). Of course, supporting it is a very very small elo hit, and my instinct would be to support it if I was commercial engine developer (which I am not

).
-Sam
You can say the same for using Tablebase or not using tablebase, since nowadays engines are so strong like Houdini, Critter, or Komodo that you don't have the need to use tablebase to increase the elo.
PS: If all that programmers care about is a small Elo gain in order to have a small edge over other engines then they should not support Rook underpromotion since it does not occur so frefuently, but people do NOT only purchase a program because it is a little bit stronger then X program, unless they are only going to use it to match it against other engines. But what about discouraging people buying an engine that does not know how to beat them with White in a position like the Saavedra endgame study.
And here is the famous Saavedra ending study game that I played versus Komodo:
[d]8/8/1KP5/3r4/8/8/8/k7 w - - 0 1
[Event " Rook vs Pawn-Ending"]
[Site "?"]
[Date "2012.03.29"]
[Round "?"]
[White "Pichy"]
[Black "Komodo3-64"]
[Result "1-0"]
[BlackElo "3000"]
[WhiteElo "2200"]
[SetUp "1"]
[FEN "8/8/1KP5/3r4/8/8/8/k7 w - - 0 1"]
[WhiteType "human"]
[BlackType "program"]
1. c7 Rd6+ 2. Kb5 Rd5+ 3. Kb4 Rd4+ 4. Kb3 Rd3+ 5. Kc2 Rd4 6. c8=R Rd2+ 7.
Kxd2 Kb2 8. Rc3 Kb1 9. Rb3+ Ka1 10. Kc3 Ka2 {Black resigns} 11. Kc2 Ka1
{Black resigns} 12. Ra3# *