/spider, founder and a lead dev says why he uses bitweaver:

"First and foremost, I need the large grain modularity so I can make my own packages and also remain with CVS for core code. Second, I need postgres support. I do not know of a CMS/Framework that offers that besides bitweaver."

/KainX says:

"I chose BW because of its superior modularity in design and faster operation (as a result thereof), not because other projects are "beginning to atrophy." Most CMS's can help you get a site up and running quickly. BW wins IMHO with its package/service engine. Instead of having to choose between a butter knife and a swiss army knife, you can build your own custom knife out of only the swiss army parts you need."

/lphuberdeau says

"bw's modularity is probably the best I've seen in a CMS simply because the modules can affect the rest of the application and not only be used as blocks"

/hawkeye07 says:

"i love bw because i can rapidly build websites simply and easily. mostly used to promote projects or hobbies"

/xing says:

"The smarty themeing system and its inidividual template file override method was great when it was still tikiwiki, however, the CSS naming conventions used to force webdesigners to deal with CSS files larger than 50kb in length. The reworked templates, the redesigned CSS schema and the logical approach to the nested selectors and the XHTML Strict 1.0 compliance have improved this to a level of professionalism and simplicity seen nowhere else."