I think the IR was still on, I just continually forget to put it in my hardware list. . . DB, if you could update it please?
As far as I know, with a standard IR port it's more a case of range, and software. After all, the Clie and other palms (Even my wristwatch) can do it, but only the clie has a powerful enough IR port to go the distance (About 3 or 4 metres, although the signal strength doesn't have to be huge at the other end)
So yeah, I doubt IR is likely to be used too often. . Being a VERY legacy device now that bluetooth is out. So it shouldn't be a worry to put in a more powerful port, in terms of battery life. use a similar "Beam recieve" program as found on the Zauri, and only activate automatically when sending data. That would work for IR control happily, as it doesn't need to be constantly on. (If you've ever held a TV remote in front of a cheap camcorder and pressed the button, you'll see the IR led only activates when the button is depressed)
With a good application, we could do well with that. . One advantage I saw before was the ability to learn codes. . . You add a new button to your onscreen remote, and the PDA begins to recieve data, then all you have to do is press the corresponding button on the remote control, and the PDA will record the code it recieves. A function like that, making the setup for the IRTVC wholly-GUI, and we have yet another thing, that linux does better than WM. (Windows Mobile PDA's need you to select a manufacturer and model, if I remember my Microsoft correctly - Same with the Sony Clie application.)