It dont look good guys.last 2 years as gone so much down hill,And last july came out with ver 2.5 with all the big talkup of something very good as yabb been runnin 10years and that was big dissapointment to alot.you been runnin YaBB Next Edition for along time but you still dont release it.This flagship site very slow and not helped yabb,who knows how long yabb3 is goin to take,why dont you ship out an 2.6 with sub-boards and all this new ajax thats runnin on this site etc etc..if this version is good to run on this site then its should be release..comon pull your finger out and start the ball rollin..am sure a release can be put together by the weekend..gettin a newer version out is better than doin nothing..

@ Michael Prager (and Corey and Jet-Li)

As SQL is 'mostly' working, and this site is not too large, is it worth making this site SQL.

My point about the perfromance of YaBB's 'showcase' site being slow - and it seems many agree - is that it scares off potential new YaBB users, particularly with the web being full of posts about YaBB running poorly (although back in the YaBB1 days, but reputations can stick).  Without new people using YaBB (due to seeing perfromance here, and reading about poor performance on the net), what hope is there?


As I pointed out earlier, it is possible to run a large flatfile 2.5 YaBB for virtually zero cost.  If putting this site quickly onto SQL (or whatever else fixes the specific issue with sourceforge) is not an option, maybe its worth considering running this site in a similar way that I manage mine.



To me, for YaBB to survive, this site has to be top priority, followed by a fairly quick release of Y3.  I imagine most existing users will want to stick with Flatfile (with the current implementations in the beta) for the performance over SQL.

Then, within a few months, drop flatfile completely and implement a true, optimised SQL.  I know that will mean some YaBBers will have to stay at Y3.0, due to No MySQL capability.

Obviously, my suggestions in last 2 paragraphs will mean extra work in writing converters multiple times, but I believe YaBB is currently backed up in a corner.



I hope my ramblings above make some sense to somebody in charge here, even if they choose another road instead . I'm heartened to see that at least discussion is going on

Okay, well seeing as my last comment wasn't very constructive, I'll try to say what I truthfully think. And before I say it, I want to remind you guys that I am here because I love the project and the YaBB name, and don't want it to die. And, what I'm about to say may surprise or even offend some of you, which I am certainly not aiming to do - I have met some very good people here (you know who you are), and some people in particular have been an influence in my life, not just my YaBB life. I wouldn't have spent so many hours mod writing or even writing this if I didn't care.

So, we all know that this needs to change; here comes the dreaded acronym which I expect to be shot down for. It's already very accepted that we have to please the users and you guys know that we have to go with MySQL - Here it is - If we are going to do that, why don't we just write it in a language which was built for it - PHP. Again, I know I'll be shot down for this, but I want to see YaBB have a future. The web has changed so much since everything was in Perl/flat file. I reassure you that to me 'personally' I don't really care what the language is that it is coded in, but like it or lump it, unless it's some complex coding that requires Perl then everyone is choosing PHP these days - there has to be a reason for that.

I know this doesn't solve the problems with devs, because if there's no devs, there's no devs - that's it - gone. But, the brutal truth is that if YaBB doesn't change then all of you know that is has gone. Brown Bread - dead!

It's already been said that YaBB needs to give the public what it wants, and the public wants PHP/MySQL. It's also always going to impossible to make YaBB compatible with other third party software because of this. Times change, so we have to change too.

Again, I'm sorry to say this, but YaBB just doesn't have a future in Perl - and if you're honest you already know that. You all know what's going on, so why pretend that it will work out. It won't work out.

Basically, I love this, and as I have said I wouldn't have spent so much of my life caring about it if I didn't... well, care. All I want to see is the YaBB name carry on. It won't happen like this. And, sorry, but just giving SQL support won't work magic. There's other software already going that's been doing these things which have been promised for years.

We are so far behind that it is unbelievable. There's websites now that are already making use of HTML₅ and CSS3 - YaBB3 is taking so long that this already needs to be considered. In my opinion the next release should be in HTML₅. We also need to be making use of JQuery.

The bottom line is, yes, YaBB is dead in the water compared to the web ocean surrounding us. Rather than carry on with half arsed updates, maybe we should just totally take a break and make an 'Elvis style come back' with something amazing.

Dare I say that XenForo has just kicked the butt of every other forum software.

I'm very, very sorry about saying this, but I know that you all know it is true. And whatever happens I will always stick by this project.

All I'm saying is, times change and we need to too.

*Now Derek waits for a massive kicikin'*

batchman wrote on Jun 11^th, 2011 at 12:42am:

Yeah, nice words Batchman. I forgot that bit, so will just steel your words - whatever happens, I would also like to thank everyone who has come before us and made this project possible, and for giving me the opportunity to practice some skills and learn many new.

CorcyraGlobal wrote on Jun 16^th, 2011 at 3:12pm:

The system, as it stands, has a fundamental problem with searching as your site grows.  Hence my feeling its future has to be SQL based. Sticking it on a dedicated server doesn't fix this issue.

Not amount of fluffy bunny templates is going to help, and certainly not where I'd like to see the limited developer resource use its precious time.

depablo -

well said, and if we had a 'like' button for posts I'd click it.  

NextGen wrote on Jun 21^st, 2011 at 5:03pm:


Sounds very intresting.gl with this projet and let us know how you get on..

Honestly YaBB is so bloated and has so many members on the dev team that it's absolutely no wonder that it takes so long to release updates.

This is not true. We have several support team members and 2 current active developers.

Why should members give a damn at all about AJAX? AJAX won't fix performance, and if implemented poorly will cost performance. Who cares about the flashy interface when there isn't even a sub boards feature or proper search?

This is not true. Ajax is a significant improvement despite how it's implemented. Even the poorest implementation results in a full page load, as it is done originally.

In case you haven't seen, I've implemented subboards for several months now and they have been showcased on this forum for quite some time.

We are rewriting YaBB  for SQL which will in time fix the search problems.

A foundation needs to be laid - with core message board features. And then more features can be worried about. But until there is a clean break, and a shift in philosophy you'll all be clinging to a sinking ship.

We have all this implemented almost as good as it gets for flat file. Why rewrite it when we have all the core features plus tons of other useful features while also excluding many for the purpose of not overcrowding the software.

I'll be coding a message board from scratch, I'm basing it off of how YaBB looks and feels, with improvements of course. I'll post more updates later.

This is pointless. There are many boards out there that provide free professional quality forums, including YaBB and more importantly hugely updated and maintained database forums. Why on earth would you create a new one?

Why not volunteer your time helping YaBB if your ideas are so novel? We've been asking for developers and we have fresh direction, just not enough people for implementation.