Part of my decision to write my own version stemmed from the fact that when I first tried out env.js, now being maintained by thatcher on github, it choked all over the very first web page I gave it. Its a wonder I noticed the errors it spit out at all, though, as env.js logs an awful lot of useless information to the console. Maybe its a unix aesthetic, but I feel solid working programs are quiet programs.
Those two minor quibbles aside, though, there are a lot of neat ideas going on in env.js. Besides, with git, I could very easily fork thatcher’s work and go whichever way I wanted to. Long story short, I sat back down with env.js last night and fed it some web pages. It did choke all over them, but this time, I stuck around and figured out what the problem was.