FibJS: Based on V8, uses fibers instead of async (opens in new tab)

It's not a joke. There is no scheduling strategy, since fibers allow only for non pre-emptive multitasking. There may be multiple fibers, but only one running at a time within the same process. If a second request comes in while another is processing and assuming that the first doesn't yield control by doing I/O, for example, then the second request isn't processed until the first one completes. If the first does yield control, then the two may be processed in parallel within the same process, just like with async/await.

You have to couple it to ImodiumJS which allows calling fibers asynchronously.

The page is “Copyright 2012-2021”, which would place it around the time that Promises/A+ was just getting started. That code example is a prime specimen of the all-too-common “callback hell” that led to the creation of promises and eventually async/await; what we’re looking at here is effectively an alternate-universe way of solving the same problem.

It sounds like FibJS supports async/await as well, but that just means there are two ways of doing things: I suspect a big reason promises won out is because they could be easily polyfilled into browsers, and a bit part of NodeJS’s appeal was using the same libraries on both sides.

Also, V8 is being abandoned very quickly because how poorly it's build quality effects development so that costant flattery of V8 seems to suggest some kind of blinders.