Question Legacy mode

In 1.0, all content mambots loaded on every page, resulting in unnecessary CPU load, also, mambots had problems running out of main content context. One of the original reasons 1.5 development started was to make a new plugin architecture so mambots could easily run in modules and components, and would only load if they were needed. Also the usual object-oriented claims were made for code reusability and so on. I did install kunnena 1.5 yesterday, and it is the last component on my stem requiring legacy mode, but I havent run any performance tests on the difference.

As to how well Joomla 1.5 increases performance may be a matter of debate. Since it started, mootools and other things were added which add >100KB overhead to the initial download, if you dont take the extra effort to remove them from the front end content.

If it's the only legacy component you're running, and counting we don't have any mambot, the performance difference isn't that big isn't it? counting plugins work in the usual way, only mambots (aka as 1.0.x plugins) are always loaded...