I believe you and DrHyde that the code sucks. I'm glad I don't have to maintain it (maintaining my own bad code is bad enough). I was writing more about what I find useful in a critique of a module. Having some bad code three years ago is different from still having bad code now. Having bad code is (sometimes) different from having dysfunctional code. When I hear someone as experienced as Barbie say they've used the module for a long time, I get a mixed picture. Critiques such as "html embedded throughout the code" tell me I definitely don't want to have to extend or maintain the sucker, but don't tell me whether the thing works or whether it would be useful in specific contexts.
The code could definitely do with an overhaul, but in terms of it's functionality and usability, it does pretty well. My thought for mentioning it, was that it may be more worth improving the YaBB code and extending it with any features that might be missing. phpBB already has a big market share and starting from scratch with something like this would be no mean feat.
I started to write my own bulletin board system, but quickly realised that to do it properly would take far too long. YaBB offers all the public facing features I wanted and the admin side isn't too bad to master. In time I may supply patches to improve the codebase, but for the moment it does the job I wanted it to.
Barbie | Birmingham Perl Mongers user group | http://birmingham.pm.org/