Yeah absolutely, open source use is great and I wouldn't expect the entire vBulletin script to be written by vBulletin alone, it makes sense to use it in some cases. But there also comes a point where the vBulletin product goes from being a unique creation to a montage of scripts found around the web all glued together. vBulletin 5 is very JavaScript heavy (which I also have my criticisms about) yet the majority of code that powers these functions is from heaps (dozens?) of small open source projects. How much of this JavaScript is actually being written by vBulletin?
I know there's two ways of looking at it, there's good and bad, I mean why recreate the wheel right? But on the other hand vBulletin customers are paying for that wheel to be recreated, not just glued together. I don't feel I should open this can of worms too much but from a developers only perspective the JavaScript (and CSS) side of vBulletin 5 is a complete mess, outdated and obsolete code included. All 114MB of it.
I know there's two ways of looking at it, there's good and bad, I mean why recreate the wheel right? But on the other hand vBulletin customers are paying for that wheel to be recreated, not just glued together. I don't feel I should open this can of worms too much but from a developers only perspective the JavaScript (and CSS) side of vBulletin 5 is a complete mess, outdated and obsolete code included. All 114MB of it.
Comment