Didn't mean to imply otherwise. I've learned quite a bit just reading his code. He has a ton of projects and I worry that he's spread himself too thin. I assumed this project had been abandoned.
I do have too many to maintain but there is such a thing as them being "done". Projects don't have to be active to be useful, plus it's open-source, I'd rather keep them around for other people to fork/leverage/maintain than delete them to make way for new projects. The real problem are the subjective ones like Jade/Stylus where the scope is limitless and everyone has a different idea of what they should have.
Or abandoned. I appreciate github projects, and seeing open issues and pull requests. Helps to make the determination if something is "feature complete and stable" vs. abandoned.
This is especially difficult with NodeJS where you have a lot of options for almost everything, and half of which is abandoned. Though, it seems to be getting a bit better and easier to follow.
Yeah, just take them with a grain of salt until you actually read the issues/pulls. Often it's silly things like "support coffeescript" etc haha, but otherwise that's a decent way to gauge a project
