Don't knock it till you try it. vB4 rocks.

I have tried it, I spend quite a bit of volunteer time helping people with their v4, and it sucks. Hard. I don't know anyone who has it that doesn't wish they could revert.

Is that your site in your sig? Look how slow it is. This is a hallmark of v4:

http://www.webpagetest.org/result/120330_SF_3SJ57/

And it's complete with a couple of 404 errors as well:

http://www.webpagetest.org/result/12...J57/1/details/

vbulletin.org is not "the company" or representing it. The question is as valid (or invalid) as yours.

You asked loaded questions, for example "My question is, what excuse does the company have?". As I already told you, "the company" doesnt need an excuse.

Symantics. A rant might be feedback, its still a rant.

yeah, we gang up on you... sure, we call this a community... a gang where everybody is on a biased side...

btw, i'm their leader, Paul M is the guy who use the whip...

I am not ganging up, I asked you because I felt your answer my be relevant to our own reasons for not upgrading.

vBulletin.org is run by volunteers and should not be thought of as the official vBulletin website. vBulletin.com is the official site and as such is always running the very latest versions.

Feed back Gone Wild.... always a good read.

This is WAY off topic, but..

I've seen those tests used as an argument against vB4 before, but you can't use that as a test for vB4. That is a test for individual site performance and has nothing to do with vB4 itself.

If it were a test for vB4, my results would be near the same and they aren't.
http://www.webpagetest.org/result/120330_QW_3SJSF/

This is after you did ALOT of work to get that type of result.

The other one tested is pretty much out of the box, not alot of work done.

Apples/Oranges and the point is, you HAD to do alot of work on the junk v4 to get decent results.

The only work I did was to properly set up my server. I did no work to vBulletin itself. Upgrades are painless for me because all of the vB code is original and untouched.

EDIT: Except for promotions.php.. that has a stupid line in the query that supposedly saves processor time and I remove it after each upgrade to allow for moving members that haven't completed the email activation to a different usergroup after 30 days.

actually, there is not a single code that would save processors or server resources... vBulletin is coded to do just that, use the best of the code and features to make server-safe transactions and processes... if you go further in trying to enhance it, you break the process...

so any suggestion to make the code better is just moronish grace... if there is a way to help, vBulletin is upgraded to fix that possibility already... no need to download a hack for that.