Taking into account the slow speed of loading of vb3 pages, I can expect this to worsen in 3.5... But yeah, seeing the AJAX technology, I was like "woah! wtf is that?".. lol.
If the developers were to eliminate their usage of tables for design, vBulletin would get a speed increase from:
Less Bloat
More Efficently Rendered Code
Lower Server Loads as a result of faster page transfers (and therefore shorter connection times)
vBulletin 3.0.x did reduce the amount of bloat (and therefore made pages transfer faster and be efficently rendered while reducing server loads as a consequence of the connections closing faster) but not to the extent as it would have if it had a tableless design (all presentation done by the CSS). Other forum software has done this:
If the developers were to eliminate their usage of tables for design, vBulletin would get a speed increase from:
Less Bloat
More Efficently Rendered Code
Lower Server Loads as a result of faster page transfers (and therefore shorter connection times)
vBulletin 3.0.x did reduce the amount of bloat (and therefore made pages transfer faster and be efficently rendered while reducing server loads as a consequence of the connections closing faster) but not to the extent as it would have if it had a tableless design (all presentation done by the CSS). Other forum software has done this:
Then again, that punBB default skin is the ugliest skin I have ever seen in my entire life. It is dull. Heck, it's even worse than the wBB default skin.
Besides, Im sure there's SOME coding that just can't be done without tables - I know that I like working with tables better than divs.