This should not come as a surprise, as it was one of the earliest items in the tracker for VaultWiki 4: https://www.vaultwiki.org/issues/2030/
At the time VaultWiki 4 development began, YUI was the only library supported by vBulletin. There was no inclination that they would ever support or ever so move to jquery. At the same time, we were not entirely pleased with YUI 2 that vBulletin was currently using.
Looking forward, vBulletin's current use of YUI 2 and other open tickets in their tracker suggested that, looking forward, we should utilize a later version of the same framework. In addition to this, we looked at both jquery and YUI3 from our standpoint as developers writing a visible source product, and we concluded that YUI3 generated more readable, more understandable code. Not only that, but at the time development began, YUI3 had some features we really needed that jquery did not yet.
When vBulletin 4.1.8 finally was released and vB began using jquery in the mobile style, there was still no greater suggestion that YUI would be dropped completely by the vB development team. It was not until vBulletin 5 went into beta, and more users like us were able to see the code, that we felt duped.
All said, YUI3 is a really great library and I'm quite pleased with it. If jquery were as readable, or it had developed certain features sooner, maybe this post and VaultWiki 4 would have been different.
In the mean time, compare (YUI3):
Code:
var posts = Y.Node.all("div.postbody");
To (jquery):
Code:
var posts = $("div.postbody");
Regardless of which library we chose, we would still be at this point right now, fighting with our live server software over the best way to compress the includes (the way VaultWiki wants, not the way the server wants).
Bookmarks