also, lets keep in mind that the original tbsource is not the highly modified tbdev versions that many sites run. Gazelle is likely a step up from the original tbsource.

The speed increases and “Gazelle is so fast” comments being thrown around are all based on comparisons between a site running TBsource and XBTT against a site running Gazelle and XBTT, so any mention of XBTT’s performance compared to a PHP tracker seems out of place.
No sense giving the credit to XBTT when the comparison uses XBTT on both sides….

So, if you don’t like Gazelle your a n00b?

Maybe the people who think Gazelle is great are the n00bs. I think most people who are disappointed were hoping for PHP5 OOP based and fully commented code. What we have seen is as bad as TBdev, its only real advantage is built in caching, but versions of TBSource / TBdev exist with that support already.

Its also annoying to read the gazelle is so fast comments, TBSource / TBdev runs a PHP tracker by default. Gazelle is at this moment in time, just a front end for XBTT. Its XBTT that provides the major speed boost, so can we give credit were credits due.

Sure TBSource is old, but it does not mean we should accept Gazelle is a major improvement, because its not.

As far as people who are hating because Gazelle ‘didn’t live up to the hype’ consider the fact that it was written for developers, by developers and was not intended to work-just-like-you-want-it-to out of the box like SMF or something similar. It’s a foundation to build a tracker on top of, not a completely working tracker out of the box. If you can’t handle installing it and XBTT, you obviously don’t have the knowledge and expertise to code and run a tracker and we’re better off without your efforts as a community; recruit someone who does know what they’re doing. It is somewhat modular, in the source layout, but it’s not completely modular (I don’t remember anyone ever saying it was) and I can’t think of a better way to structure the code, for the goals that they aimed for.

That said, there are some glaring faults with Gazelle. It’s not a tracker-foundation as much as it should be, it’s not a vanilla source code set, it’s what.cd source and it was developed as what.cd source and not as a proper FOSS project. Their code quality is vastly inconsistent, ranging from nearly tbdev quality nonsense to on the verge of utter brilliance, which makes it a pain in the ass to modify particular things or to familiarize yourself with their source. They say that they had a formatting scheme, and yet their source code does not follow one much at all. Everything is cached to the point of ridiculousness, and rather than cache things transparently when they were cached, it seems that everything was cached first and then transparency added as an after-thought. The initial weeks of gazelle launch at what.cd are a testament to that.

There’s a list of complaints about the code a mile long, but the point is that it’s a billion times better than tbdev is or ever will be, it has a sane db schema and is fast as shit, with or without the caching. I haven’t seen a good argument as to why it’s unacceptable, other than just general hate.

Gazelle is the future of the private tracker community, like it or leave it. It’s not perfect, but then again, we all need something to strive for.

Back on topic. Gazelle is amazing. If you don’t like it then don’t use it. But I’m pretty sure that most new torrentsites will gladly use it. This is not about waffles vs. what, they’re both great sites, but soon you’ll find gazelle on various other sites too.

The only thing which I don’t really understand is why they don’t use Opentracker as the tracker, afaik it’s the fastest tracker to date (TPB uses it, and if theres a huge tracker then it’s TPB).

Ah yes, I guess it’s an RC for no apparent reason at all.

*dumbass*