Yes, its more trivial than the concept of wait() which is expected to be understood by everyone here. So yes, I consider this as trivial.
No, it's not. I'd bet most users only understand wait as "Leave the function for now and continue from here next frame". Many beginners can get by thinking it's just something you have to put at the end of while(1) loops. Most people here are C-Script/Lite-C programmers, not Windows C programmers.
Neither am I a Windows C programmer. A mutual exclusion is much easier to explain than "hey, it returns from the function but in the next frame it resumes the function". And a linked list is the easiest data structure available in C (yes, even simpler than arrays). They make sense in every way while wait() makes no sense to a beginner.
"Hey, you must add a wait(1); to you loop, otherwise your program will crash" and "I'm not sure, have you tried to add a wait(1)?" shows that most people don't really get what wait() is but its assumed to be the magic healing potion for code. wait() is NOT trivial. A linked-list-mutual-exclusion-thread-factory is, compared to wait(), trivial.
