We're using Scheme in our startup and I recommend it. Our web app is built in Kawa and runs on the Tomcat server. We had been using the PLT web server but left

We're using Scheme in our startup and I recommend it. Our web app is built in Kawa and runs on the Tomcat server. We had been using the PLT web server but left over some concerns with the way it was using memory. They've fixed that and now I think switching was a mistake - we should have just stuck with PLT. Kawa... hoo boy. It's got some issues. It's still Scheme, though, mostly. So for the web I would use PLT and its great web server. In fact I do use it for a little internal app and love being able to write a web app in the 'direct style' ie just write a web page interaction with a user as a function execution. You can just assign a lambda to a link, saying 'when the user clicks this link, execute this lambda'. It's great. However, that links won't be bookmarkable nor indexable by search engines, so if some of your pages need to be, you have to make the links to them be traditional links. So the continuations-based stuff lends itself to the parts of your app that are private to a single user (like taking user input or showing them their email) and/or shouldn't show up in a search engine anyway. This would include anything that you would describe as a 'wizard'. NASA (or is it just the Air Force?) is using PLT Scheme to control a large telescope in New Mexico (http://news.ycombinator.com/item?id=75219 http://news.ycombinator.com/item?id=75219) to great success. So for soft real-time stuff you should be good. Just from using it, I wouldn't recommend the default garbage collector with PLT for anything like hard real-time stuff. But there are other GCs, so ask around. The PLT mailing list is excellent: http://www.plt-scheme.org/maillist/ http://www.plt-scheme.org/maillist/