Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: ergophobe
Has anybody got experience with each of this. Please advise both from the point of view of installing and maintaining the softwares to ease of modifying themes for the scripts.
I am the author of Drigg, so my opinion is biased.
I only really know Pligg and Drigg.
Pligg has been around for a long time. Its weaknesses are its db structure, the source code (not the cleanest) and the the fact that theming it is not the easiest thing to do.
On the bright side, Pligg has a large community, version 2. is coming soon, and there are several themes already developed.
Drigg is a newer project. It is now in active development. Its weaknesses are that it's heavy on your MySql server (that's true for Drupal), it's harder to configure (because you get a whole Drupal system!) and it takes a while to get around it.
The bright side is that it's really well coded, there is a strong separation between code and presentation, and it has a good db structure. ALSO, you get the full power of Drupal. You can have forums, and whatever else Drupal offers. Have a look at [drupal.org...] -- there are modules for all sorts of things you might possibly want.
Anything about scalability... meh. I don't think anybody has done a full comparison between the two, but at the same time there are some major sites based on Drupal out there, very major sites, and they seem to be managing OK.
Drigg has a huge list of feature requests which are slowly being worked on.
[edited by: mercmobily at 4:23 am (utc) on Jan. 26, 2008]
I should add that:
* Drupal does scale. You might need memcached, but it will scale.
* Drigg's development is going right ahead, whereas Pligg's development seems to be stalled
[edited by: engine at 7:30 am (utc) on April 14, 2008]
[edit reason] See TOS [/edit]
As for the rest. Check. Got it. Understood. "All you are saying, is give Drigg a chance."
Since both are free and open source, I can only suggest that anyone interested Pligg, Drigg or what have you, install both, run Apache Bench or some more specific script designed to stress test (i.e. to do inserts as well as just request pages) and see which meets your needs.
Short of that, it's all hearsay.
Perhaps more to the point, though, I see people all the time who have never built a high-volume site (for example, ME), who obsess about scalability, certain that their idea is so hot that the data center is going to have to put in additional air conditioners to cool the place down with the load their site will be creating. If Brett or Dries or Matt [choose last name] is starting a new site and he thinks it's going to go big, then I would say that scalability is a serious consideration. Usually, it's not (think of all the people who worry about forum software scalability and then have 500 threads after two years).
Since my sites churn along at 10K visits per month or less (usually anyway), I just don't worry about scalability (oh! shame on me!?). If something starts getting 10K visits per day, I'll rewrite and scale then, but it hasn't happened for me and doesn't happen for most people with killer ideas for the latest forum/tagging/digg-clone/etc site.
I know of people who have had site ideas for several years who never launch because they can't find a scalable solution and, as it turns out, you don't need any software at all to handle zero hits per day.
All things being equal, I would rather have the most efficient solution, but all things are rarely equal. So personally, assuming that it's going to be one of MY sites (i.e. a few thousand visitors per month), I would go with whichever one is easiest to administer and has the feature I want, provided it passes a basic stress test.
Recipe for actually getting a site built: prototype, launch refine.
Recipe for having the best idea that never leaves your hard drive: prototype, refine, launch.
And FWIW, the latest test results I've seen comparing Joomla, Drupal and Typo3, show Drupal performs the best if all of them have caching on. Still, it ain't fast and light and never will be compared to something designed to do only one thing. So many DB queries and includes to produce one simple page. Cache cache cache. But it still has its limits, but since The Onion runs on it, I don't see myself ever reaching those limits. Maybe I don't dream big enough, but the things that interest me are generally too obscure... I'm a jack of all things long tail if there ever was one!
As far as i can remember the PLIGG owner tried to sell PLIGG. Maybe support might be broken today.
As for DRIGG, i can' t remember it clear, but the good is that you can use the whole DRUPAL module system if you like. The maintainer offers a full system for download and in my case i had a running base system in 4 or 5 minutes. The only problem i remember was a URL problem with the UTF-8 transformation of umlauts and french letters. MySQL storage was OK, but not the URL. Sorry, forgot it, but if you try the DRIGG forum, there are one or two threads. Maybe it is fixed now.