To add to JPMonkey's comment and without knowing what your trying to achieve, in some cases it is better to distribute the logic across a few micro-controllers than to try to multitask it all in one. As soon as you start multitasking you loose some of the tight control of code you had and chose a micro-controller to deliver and therefor the system as a whole becomes less predictable. This does not include the use of interrupts, interrupts are a great way of diverting to a separate very specific task that an external event has triggered, interrupts are often used to run code that otherwise would be implemented through repetitive polling or other inefficient means.
As with everything, there are always different ways to get the job done, let us know what that job is and we can better advise you
To add to JPMonkey's comment and without knowing what your trying to achieve, in some cases it is better to distribute the logic across a few micro-controllers than to try to multitask it all in one. As soon as you start multitasking you loose some of the tight control of code you had and chose a micro-controller to deliver and therefor the system as a whole becomes less predictable. This does not include the use of interrupts, interrupts are a great way of diverting to a separate very specific task that an external event has triggered, interrupts are often used to run code that otherwise would be implemented through repetitive polling or other inefficient means.
As with everything, there are always different ways to get the job done, let us know what that job is and we can better advise you
