Mambo was released as a product by Miro sometime in 2000 if I'm not mistaken...
Considering it probably was in development for a year before that lets assume it was started in 1999....
WCAG 1.0 was defined and accepted in the same year 1999...
At the time most people had not considered that ALL pages should be WCAG compliant that wasn't an issue until much later on and the advent of WCAG 2.0 which address many of the shortfalls of the 1.0 standard...Some time around 2000 or 2001 where the WCAG was being widely accepted as the way to go...until then it was an accepted standard but not anything that was a required (hell it's only required in a few places right now!)
Drupal was started in 2000 and wasn't released until 2001....
So essentially Mambo was released before Drupal was even thought up...That gave Drupal the leg up on meeting the new standards since they had no code locking them into a box that would limit how they implemented the WCAG....
Now it could be argued that well this framework redesign should have been done before now and if it was a commercial product it probably would have been....
but I think the timing is just right, We have the WCAG 2.0 standard defined, new emerging technologies such as Ajax have come along and since you don't want to have to reqork the entire framework each time something new comes along it makes sense to wait until there are more than just one reason to go through the monumental task of an entire framework rewrite...
And from everything I have heard from the devs about the new framework it should be expandable and easy to upgrade for many years to come!
Not only did they manage to break the chains that have limited them for so long the developers managed to come up with a framework that can easily transition users to the new system without breaking every website running the old framework.
And as time goes on and the new output system is implemented it won't matter what WCAG may come oput with as the output modules can be easily replaced and upgraded....
Quote:
You talk about 2 or 3 features to beat Drupal. Which features? Do those features imply a really hard work? And the Drupal features... are you talking about the 4.7 or the 5.0?
No they don't require a lot of hard work...at least not anymore...Time consuming and a lot of thought maybe...but most of the hardwork has been addressed in the framework.
Right now the only things that Drupal really has that Joomla does not is a very good ACL system/user leveling and standards compliant output...
Now J1.5 doesn't address those directly...what it addresses is the ability to address those subsystems easily for development.
J!1.5 is the bridge between the old and the new...
It is essentiually the new modularized framework using the old framework's modules to ensure compatability...
Now the work to make a WCAG compliant output module and a better ACL can be started.
these will bring Joomla up to version 2.0 where the main differences between Drupal and Joomla will be in the 3pd module and component support.
Right now there is not a whole load of difference between the two in that regard other than the fact that Drupals add ons can draw from the ACL and output routines that already exist in Drupal!
And the work that needs to be done on those two feature sets are not as hard of a challenge as it will be to make Drupal as user friendly as Joomla currently is...
So when I say it will be easier for Joomla to overtake Drupal that is what I have in mind....
The tasks that Joomla has to do to give you what Drupal currently gives you are easier to imp-lement than what Drupal needs to do to make their system do what Joomla currently does....
They are both fine products and I could not say to anyone don't use drupal unless I know they are technically not up to the challenge...
But 1.5 has opened the door to going beyond Drupal in it's current form in fact maybe it has even learned a few lessons from how Drupal has done what it does and the future of Joomla as a Application framework that is easy to operate makes it the more promising package to invest in right now!