I agree with you the storred procs are more work to maintain than just having embedded paramterized sql statements and while there may be a performance gain by using stored procs it would be so small that its hard to measure. I guess I've gone down that path with MS SQL because I was raised that way and was always told it was better to use procedures and told people that myself over the years and believed it but over time its less convincing. Still its neither a bad practice either, its just more work but there are some other benefits that may matter in some situations. For example you can harden an MS SQL installation by using a user in the connection string with no direct permission on any tables such that they only have exec permission on some stored procs. Of course while this is good for security it will cause inconvenience when upgrading the site because upgrade sripts will fail if they don't have permission to modify the schema so hardening the intallation also leads to manual upgrading instead of automatic. Like you say its more of an issue in "enterprise systems", but you know I do hope entrprises use mojoPortal and I am trying to build it for such. Still, no reason for all developers who make custom features for their own needs to use stored procs unless they see a need for it.
With MySql, I started out with version 3.x of MySql and stored procs are only as of version 5 or newer but I really feel no compelling reason to start using them right now though I reserve the right to change my mind later and start using them I dubt I would ever go back an re-write everything using them thats just make work.
Best,
Joe