What is the reason for the indifference to CommonJS? I understand you are no longer looking to adhere to it.* Are all contributors abandoning it or just you?

If you were not happy with the quality of specs or suitability to your environment, would it not be possible, as with the WhatWG group of browsers for the W3C process over HTML5, to use your weight as the apparent wide lead fore-runner and stake-holder among SSJS implementations to influence the CommonJS process (or something similar) in a way that accommodates your needs as well as offers some room for collaboration? For example, maybe you could express openness at least to a veto power to avoid dictates coming from specs you did not find to be well thought out?

I would think everyone would benefit as a result, since CommonJS too should not acquire so much adoption if the fore-runner is resistant. (I'm not speaking with any knowledge of the history or processes at CommonJS, just wishing for a break to the standardization impasse.)

Developers such as myself really like the ability of using JavaScript on the server (and there ARE plenty of cases of code reuse between client and server), as well as having cross-server-side portability, so I hope that you do not become the IE of the SSJS world by stifling compatibility through dominance (not as the IE of the stagnant years, mind you, but as the IE of the IE-Netscape browser war days when it was innovating and ultimately successful, but wasn't harmonizing with other players and thereby set the stage for years of agony for developers).

* http://www.reddit.com/r/node/comments/h1m2o/i_am_ryan_dahl_creator_of_nodejs_ama/