It seems to be a popular sport around here. We all come to 8051s with different backgrounds and experiences. If we plan to be productive 8051 programmers we all have to come up with some kind of framework that allows us to provide the illusion of multi-tasking on the 8051 (and by that I mean the keypad works and the LCD works and the LEDs work and the motors and other inputs and outputs all appear to work -- all the time).

I know I have my system and I am quite happy about it. It is deterministic to the degree that I require it. "Tasks" (or "jobs" if you prefer) get "scheduled" as required, timers coordinate periodic events. The only real difference between a lot of these alleged OS's and what you and I do, is that the creators of these alleged OS's have published their ideas (web, magazine, book). I'm sure if you spent some time to put together a few thousand words describing how to utilize your framework you'd be happy you did (published or not).

I enjoy reading about these endeavours and much can be learned from them. I once did a project with a real RTOS on an HC11 and it was quite fun and suitable to the task. The 8051 I use now is much more capable than the HC11 (except for the stack), but I would not generally choose an RTOS. But to bash people who publish alternative frameworks is not constructive. And we can all learn a lot about software engineering by allowing ourselves to learn new languages and techniques and to read about the history of operating systems and the like.