RT-Thread

If RT-Thread is judged only by tasks, semaphores, and queues, its main value is easy to miss.

RT-Thread is not only an RTOS kernel. Around Chinese MCU and IoT projects, it provides an engineering environment: BSPs, a device framework, FinSH, filesystems, networking, packages, configuration tools, Chinese documentation, and community support.

The first model is:

FreeRTOS: lightweight kernel entry point
RT-Thread: RTOS kernel + device framework + IoT component ecosystem

This is not a replacement story. The default system boundary is different.

When an MCU project chooses an RTOS for the first time, the first questions are often about size, speed, and API simplicity.

Those questions help, but they are not enough. Choosing an RTOS is not only choosing a scheduler. It is choosing how device software is organized: how tasks are created, how drivers are integrated, where networking and filesystems come from, how board differences are maintained, whether existing C or POSIX-style code can be reused, and whether the team can debug field failures.