<p><pre><code>    &gt; Welcome to the world of embedded RTOSs, where
    &gt; everything is running within a single application.
    &gt; There&#x27;s certainly no memory protection.
</code></pre>
Generally, I agree, even though there have been quite a few chips already that have a primitive &quot;Memory Protection Unit&quot; that typically only distinguishes two processor states and you&#x27;d be able to protect the working data of e.g. the scheduler and your watchdog from the rest of the code running on your system. Which is much better than nothing!<p>But in the end the important consequence is: Having everything in one address space encourages people to violate the concepts that memory protection between tasks on your PC typically enforces, e.g. tasks reading from, and writing to other tasks&#x27; data structures without proper synchronization; instead of using proper IPC mechanisms like queues. Which is probably what these 10&#x27;000 global variables were used for.