A practical discussion of when to use a round-robin (bare-metal) loop versus an RTOS for embedded systems. Two round-robin styles are outlined: a simple main loop with state machines, and a scheduler-based loop with time slots. An RTOS provides independent threads and synchronization primitives (mutexes, semaphores, message queues) but adds code size, licensing costs, increased interrupt latency, and a steeper learning curve. Key decision factors include timing requirements, Rate Monotonic Analysis, code reusability, and whether the system complexity justifies the overhead. Reader comments expand on hybrid approaches, state machine design quality, and resource constraints on small MCUs.
