C#.Nick

In a word: Yes.
In two words: Kinda Sorta.

I'm evaluating whether it's better to continue rolling my own, or to contribute work on an existing project. SubText has potential, doesn't seem to have tons of people actively working on it, and would benefit from someone else actively working on it. Lots of the issues I have with SubText seem like they'd be easily fixable. My main problem is working with the SubText codebase. I'll be honest: I don't like the code, and changing the way it's fundamentally structured doesn't seem possible without basically rewriting large parts of it (basically writing my own blog engine).

This is after just a cursory skim of the code, I could be wrong about how much work it would take. The lack of OR/M, and the extensive use of some kind of funky web control architecture scare me, however.