Yeah, the current style is like, not aimed at mobile devices at all,
. UI components are too small / fiddly imo.
Also, what I gathered is that after vB 3, the product went into a different direction - idk how much these bulletpoints are related to each other though:
* The original company, Jelsoft, were taken over by some company
* An effective rewrite was announced, changing the back-end code to follow the MVC paradigm, with the eventual goal of making the codebase easier to maintain and expand, especially for people that didn't originally write the code. This in general is a Good Thing, but probably not for PHP - since it's an interpreted language, more abstraction layers means more code and code paths executed, means longer processing time for effectively the same result.
* The original / core developers and product manager (iirc) packed up and left to create Xenforo
* (I think) vB 5 went towards mobile: the product was split into a back-end and front-end component, so that the native mobile client and web client could talk to each other. Again, this is what I consider a Good Thing, and it's how I've build web/mobile apps for the past three years, but compared to the approach in vB 3 it's not any faster.
I mean it could be faster, but they'd have to do some serious optimization and rethinking. Maybe running it in Facebook's HHVM would make it run a lot faster; instead of an opcode cache, it's a complete virtual machine, which can compile to native machine code on the fly / as needed, like the JVM does. I did a quick google search but couldn't find any experiences running vB on HHVM. Maybe I should try and fiddle with that myself.