And hopefully, manufacturers will agree on a standard set of commands, to the extent possible, and avoid the Tower of Babel situation we have now, with the different formats and protocol sets used for no clear reason other than to lock you into buying and using "their" remote (yes, you can get so-called universal remotes, but they are a pain to set up and have other issues).

What does this mean for the future of IR? It's not clear. RF4CE offers much more functionality, communication beyond the line-of-sight, and two-way links. No more hunting for that remote control, as you'll be able to signal it from the product it controls to have beep at you and say "here I am." And let's not forget what a potential business opportunity it is for component vendors, as well.

The IR remote has its virtues: it's very cheap, takes little space and power, and fulfills its basic purpose fairly well. It's become truly ubiquitous: you can find it embedded into inexpensive home appliances such as coffee machines, heating pads, fireplaces, curtain controls, and ceiling fans, just to name a few uses. But it has drawbacks, too, with its limited, direct-line range; simplex connectivity; and problems in applications in areas of bright ambient light or sunlight.

It will be interesting to see what traction RF4CE gets over the next few years. Will it push IR out of the way? Will it stumble? Will it be a peaceful IR-to-RF evolution, or a revolution? Will RF4CE brings us closer to the "universal" remote control we keep dreaming about?

Or will peacefully RF4CE coexist with IR in lower-end appliances, and RF4CE in higher-end ones? Let's see what happens.♦.