"I believe that the choice between Classic, Threads, and Open Topic should be based on the technical solution that one seeks. Don't have MySql access - take Classic. Want a database-driven solution - choose Threads. Prefer a full package including hosting and maintenance - go for Open Topic. After all, this is the main decision that a prospective client has to take."
That's the crux of it right there.
I'm absolutely sorry if you bought a .threads board thinking that it was UBB.classic on MySQL, but it is not. That's selling it short, actually. It isn't now and isn't going to be UBB.classic on MySQL. It has it's own feel, it's own model. It's smaller, lighter. It's threaded.
It is a lot of things but it isn't UBB.classic size medium.
If you are buying on of our products based on "small meduim or large" I submit to you that either your using the wrong basis for your decision or I've done a bad job on our product pages relating the fact that UBB.threads is NOT UBB.classic size medium.
Could the UBB.threads interface use some refinement? Sure, certainly. Will it turn into UBB.classic? I don't foresee it.
<img src="http://navaho.infopop.cc/golf.gif" alt=" - " />
