psTubble27
Well-known member
Problem with IPB is that while the product is stable, it is also very bloated in its code-base (for the reasons I describe below). Things take circuitous routes to draw anything on-screen (a bit like VB), while demanding expensive hardware just to perform elementary functionality. In other words, it will always scale badly, and feel more sluggish to your users. It will never have a near real-time performance, I.e. as if you were browsing your own local computer files or something, ie. -- 1-sec response time. And in case you think no web application can have that, see this:IPB - going quite a long time, communicates to their customers about the future and has a very powerful and stable product
http://xenforo.com/community/threads/real-world-page-loading-speed.1215/
Consider that XF's efficiency is not an artifact of it being young, but a design feature from it first being announced. Its whole architecture, and just ask add-on devs, its whole API structure, were arganized around this. IPB (not to mention VB) is never going to be able to reach that kind of efficiency, short of rewriting their code from scratch. And the reason IPB has been able to stay afloat unlike VB was by keeping the bloated "working" legacy code-base from 8-9 years ago.ibaker said:XF - very young