Interrupts and polling
Not really. 

Polling requires CPU cycles to poll a device and respond if needed. Detecting interrupts takes up no extra CPU cycles and is almost always done in parallel with instructions being executed. CPU cycles are only used up in servicing the interrupt. 

Also, with polling, you have a control over how and when you poll devices whereas interrupts are generally out of sync with the program (or at least, you cannot exert too much control over when they arrive).

The mindset behind polling driven and interrupt driven code/architecture is entirely different.