Paper: https://people.cs.vt.edu/~dongyoon/papers/EUROSYS-17-NodeFz.pdf https://people.cs.vt.edu/~dongyoon/papers/EUROSYS-17-NodeFz.... Very interesting. From w

Paper: https://people.cs.vt.edu/~dongyoon/papers/EUROSYS-17-NodeFz.pdf https://people.cs.vt.edu/~dongyoon/papers/EUROSYS-17-NodeFz.... Very interesting. From what I'm reading it's a novel approach: >A remark from one of the developers inspired the approach we took to Node.fz: “Unfortunately, I’m not able to provide a simple test case because I dont know how to artificially expand the delay between the ‘timeout’ and ‘close’ events.” Using Node.fz, developers can do this and much more >Node.fz amplifies the non-determinism in Node.js using the techniques of de-multiplexing, event shuffling, and event delaying, achieving a greater exploration of the possible application schedule space without requiring any developer intervention. As a drop-in replacement for Node.js, developers can easily make use of Node.fz during development and test and then seamlessly switch to the optimized Node.js binary in production. Developers then have the assurance that their applications will be stable under a wider variety of deployment conditions. As the article mentions, I wonder if the code for Node.fz could be released. Would be cool to play with.