busy-waiting can be bad, as any time-delay technique can have synchronization issues which will cause inconsistent results and also continuously checking for completion of a process wastes the computer's resources; however, sometimes busy-waiting is actually more practical and can decrease the overhead of alternative synchronization methods (like in low level programming)
gogogo
in summary, busy-waiting, in a way, takes up a processor that could have been used to execute something tangible.
busy-waiting can be bad, as any time-delay technique can have synchronization issues which will cause inconsistent results and also continuously checking for completion of a process wastes the computer's resources; however, sometimes busy-waiting is actually more practical and can decrease the overhead of alternative synchronization methods (like in low level programming)
in summary, busy-waiting, in a way, takes up a processor that could have been used to execute something tangible.