SS Dev Team,
First off, I gotta say this is a pretty sweet script. I've played with quite a few CMSs, and I love the simplicity of management and integration that SS provides.
That being said, I just tried installing 2.2.1 on my live platform (Apache 2.2.6 [Unix], PHP 5.2.5, MySQL 5.0.45-community-log, shared-hosting at bluehost.com) today, and encountered the 'Allowed memory' fatal error before it even finished installing. I had to increase the memory limit to 96M ( trying other values in the 60's and 80's before doing so ) to get the install, and the subsequent flush, to complete successfully. And even after that, a vanilla install wont run without the limit set >= 48M . I've searched the forums, seen that others are having the same issues, and noted the suggested work-arounds. They've worked for me (generally).
But guys, really. It isn't reasonable for a script to require so much memory. Especially for shared-hosting environments, like my live environment. They frown severely upon memory hogs. Joomla? Drupal? Never had issues with them, running under the default 32M. And they can get rather complex in terms of functionality... A little too complex, in fact. Joomla/Mambo expecially. Too much of a learning curve for non-savvy end-users like the people I'm developing for.
SS seems to be the best option for my needs... and I'd readily embrace it if it weren't for show-stopper issues like the memory issues. How does SS differ from CMSs such as Joomla or Drupal, that it requires so much memory? What tactics do they employ to manage memory demand, that SS does not? I'd pitch in and help optimize if I had the necessary PHP skills, which unfortunately I do not at the moment... but for right now, I'd at least like to understand whats different, hear the explanation for such a high requirement, and perhaps hear what steps are being taken to minimize the demand on memory (and when we can expect them implemented).
Thanks for your time, and an otherwise pretty darn awesome project!