As someone who wrote something similar (<a href="https://github.com/olegp/common-node">https://github.com/olegp/common-node</a>) back in the day before async/await, I have to say that I don't see much of a need for this nowadays. The only feature that's still useful that I can think of is the ability to run the same code on V8 and the JVM.
I think this is a hoax/joke?<p>The performance test is bizarre, and literally nothing in the development guide ever shows anything but single-thread serial code for i/o.<p>What, exactly, happens if a second user accesses the website while a request is processing?<p>Also the docs don't explain how fibers are being used -- what is the scheduling strategy? Is there even more than one fiber?
The docs are so disingenuous<p><a href="https://fibjs.org/en/docs/guide/about.md.html" rel="nofollow">https://fibjs.org/en/docs/guide/about.md.html</a><p>The comparison doesn't do half of what the original did. Bizarre
Is it just me, or does their example of the traditional way of doing those calls user literally the least efficient possible way of writing that code?<p>Surely using async/await would get you to something nearly as clean as their end-state