> Yes, FastCGI looks really cool. > > However, in my particular case, it's not like I am the only one who does > some work on the website, and I'll not be around forever either (it's > volunteer work, basically). Using straight PHP is technically inferior, > but is much more likely to actually be used by the next guy. Not to > mention that just spitting out a page is a lot easier than dealing with > caching stuff and the like.
Well php can be used as a fastcgi server actually. > Is there a specific language, though, that you could recommend, because > that's what we started out talking about? I think depending on your knowledge and needs perl, python and ruby may be eligible do to the job. If you plan on spitting out html directly from your code, I'd say use whichever you're most familiar with. If you need something more complex, then have a look at the maypole, catalyst, cherrypy and ruby on rails projects. The key element while trying to decide on a web technology is not to choose the hype technology of the day but evaluate each solution.
