@sreich I have two major use cases:
* Asynchronous Resource Loading (mandatory on JS and Flash) and desirable on other targets though, you can "emulate" using a thread
* Coroutines allow you to have hundreds of "processes" with a very small memory footprint. If you know DIV/fenix, they used the process concept that it is a green thread/fiber that were more lightweight than a proper thread. Coroutines are even more lightweight and do not require an implementation at the system level (fibers/thread scheduling/ keeping registers)
* You can use it for example to linearize without callbacks stuff like: I want to do this tween, and then do this other thing, and then this other, and I want to repeat this three times. You can do that with promises or a very complex callback implementation, or just use coroutines and do a tween call, and a plain for 🙂
* EVE Online uses stackless python for its backend, that use a lot coroutines
* The actor/process concept DIV like. You can implement entities that act following a behaviour that can be read like if it was a thread instead of a state machine that could require more work to understand or update. This is pretty cool.
Regarding to the website: yeah, It's not ready yet.