In reply to Andre.

Joomla is one bloated beast. PHP is not real memory efficient my friend and Joomla is quite memory hungry. The Joomla core I've had run in's with. They refuse to even document their own code API wanting someone else to do so. They jet-set around making money at seminars pretty much on others work. Joomla is not a great CMS at its core, in fact e107 is far better. Look at the code, simple as that. What makes Joomla so good are the components and modules delivered by third party ISV's.

The Joomla core went and decided that anything in the Joomla repository must be GPL. Citing they are all about open source. Yet, wont document their own code. Will not allow developers to effectively protect their own code.

How many people do you think would appear at a Joomla Seminar and they are paying for the privilege being charged MONEY (in the TRUE SPIRIT OF OPEN SOURCE LOL!!!) if all those third party developers work did not make Joomla the name it enjoys? Answer none.

Yet they choose dictate to those ISV's while they jet-set about making gobs and gobs and gobs of money from seminars. Nice. Travel, tell others how wonderful they are (I've attended one, ego manics yet wouldnt last a week working at Microsoft or Google) and what a wonderous application Joomla is. Its HILARIOUS really to see so many people duped but not so much so when one realizes what they actually are doing.

The Wordpress developers have obviously a better knowledge of what web means: Use as little Ram as one can, have code move as fast as it can given PHP's obvious rather horrid boundaries as that equates to sessions.

I believe its Hewlett Packard who has a stress test tool. Throw that at a Wordpress site, Drupal Site, DotNetNuke site, e107 and Joomla and Liferay site with similar content.

You will see DotNetNuke will stay the most steady, its built enterprise so rightfully so. Perhaps should not be in the equation. Liferay coded in Java is again, enterprise capable. Performs better than all mentioned under traffic loads.

e107 in PHP does best. Wordpress is next in line, then Drupal and lagging considerably behind is Joomla.

I did such test years back when I was working with Joomla. When they went "MVC" citing "MVC" as a big revelation and the community awed over it. Oooo... Model View Controller. Fantabulous new buzzword yet has existed since the late 1970's just few applied it to the web.

For enterprise level applications on the net MVC makes lots of sense (and also not so). In PHP makes less sense as all overhead equates to munching memory and cpu cycles in a non-threaded environment. PHP remains one of the absolute few languages web ready that soesnt support threading. Nice.

If you take a look at CPPCMS a framework you will see it just runs rings around every PHP framework in existence. In 2013 I wrote a small application with PHP, it'd handle around 1100 connections before its memory usage and putt putt behavior impacted it. I ported it to CPPCMS and behold, over 28,000 connections and still had ram left to spare. Was the hard disk became the bottleneck.

PHP is of course written in C++ which never made much sense to me. But I am sure they laugh all the way to the bank on that one. Code it in assembler, that makes sense. But then we might need understand how CPU's and computers work and that sounds like work.

Then look at Microsoft's MSIL which VERY closely resembles assembler and begin to understand why PHP is already dead and doesnt know it. In fact a friend of mine at Microsoft informed me that by .NET 7.0 (currently at 4.5) .NET will run 95% speed and efficiency of C++ now.

Thats game over for PHP perhaps Java as well albeit not as soon.

As a developer making web applications its all about goals:

1. Wordpress is not meant to be an enterprise CMS nor is Joomla. Under heavy traffic Wordpress will outperform Joomla significantly as the developers at Wordpress apparently realize that its important since its not enterprise not to eat ram memory like a pig at a feast and use every trick in the books to save CPU cycles as those equate to user sessions.

2. Wordpress supports their developers by providing excellent documentation to those developers about Wordpress functions. Joomla does not, even years later after the MVC transition they still do not.

3. Wordpress is EASY to use with a good amount of thought into the user interface. Hand a Joomla built site over to a client who knows nothing and watch as they get frustrated and upset. I've done it.

4. Wordpress documents how to use Wordpress. Joomla doesnt know where to begin as they will loose the average user in scant time.

5. Enterprising (and yes thats the word) entities like Weebly are the ones who are enjoying the frustrations as people just want something they can learn, easy or at least fairly easy, understand and start with. Both Wordpress and Joomla are handing Weebly webmasters.

Joomla would not have a clue as to how to take the spaghetti interfaces they have made and create a truly drag, drop, associate, set properties and go CMS.

Wordpress IMHO should do two things... scratch that, three things:

1. Make Wordpress backend competely drag, drop, associate, set properties environment. That will do away with any concerns over other open source CMS systems having a market share. Thats game over for Joomla, e107, Drupal etc. for 99% of case use sites.

2. Get real flexible workflows built into Wordpress (thats a biggie) and make it as simple as the task can be. That puts the nails in all open source competitors except enterprise level.

3. Start working on a new Wrodpress application from scratch in .NET