Surely, and sometimes what is needed is a plain webserver. Sometimes, a scripted server, and sometimes a full blown content manager. Very few organizations can effectively support more than one webserver. So please don't be offended if sometimes I use the Swiss Army Knife to just cut a string.
In my usage model, the system administrator is responsible for providing applications (cgi, adp, whathaveyou), and individual website masters provide their own content. So, we need separation of filesystem space to allow for ftp accounts and so forth. Once the administrator has made the subsite, and associated it with the ftp accounts, home dir paths, logfile paths, and so forth, then the site master can choose what to use. If they want to create plain html pages, that's their affair. Of course, they often ask for similar features, and don't care how they are provided, so the OpenACS/AOLserver combo is quite nice.
To me, the *interesting* part of OpenACS is that a single platform can provide support at the basic, scripting, and full-on-bad-mojo level.
Cheers!
