What do you mean by common.js implementation? The only thing I know of that survived the common.js movement was that node.js adopted it's module file format.

What do you mean by common.js implementation? The only thing I know of that survived the common.js movement was that node.js adopted it's module file format. That format requires either sync I/O, XHR loading and wrapping or a build-step or build-server to use in the browser. There are libraries out there that try to solve the module problem in the browser, but there are certainly no clear winners and nothing that doesn't have serious limitations or drawbacks in one way or another. Also as I mentioned and you quoted, I found a great way to load common.js modules in chrome apps that nobody had done before, but it only really works in that unique environment. But modules are just the tip of the iceberg. I need a way to handle I/O actions, streams, TCP, fs, db, etc. All these interactions and APIs need to work cross-platform in a variety of different runtimes. I can't even start implementing git clone over a TCP socket till I have a TCP socket API to program against. But like I said in the bountysource, most of that is all now solved more or less. I have a much better understanding of what needs to be done and I am starting out this phase knowing how git works internally down to even the huffman encoding bits inside the deflate inside the objects inside the packfile stream inside the git clone stream. I also have more time this round and less conferences that I have committed to speak at or visit. (I think I only have two more trips the rest of the year actually)