| Hi, This reply is a bit late because someone pointed me at it and suggested it was worth answering. ...so I hope that this is useful! I have experience using Chicken Scheme in production both on knodium.com and registers.app Both times it has gone well. There's an HTTP implementation ( https://api.call-cc.org/5/doc/intarweb ), a webserver (https://api.call-cc.org/5/doc/spiffy that supports SSL) and an HTTP client ( https://api.call-cc.org/5/doc/http-client ). There's also an "app server" that tries to be like other app servers you might already know ( https://api.call-cc.org/5/doc/awful ). We had to write a lot of our own stuff but it fits fairly neatly into the scheme-way of doing things: you can get a remarkable amount done with just a few simple lines of code. I'd probably want to write about as much in any other language as a lot of what we built were domain level abstractions. Knodium is now long gone but there's a video of what it looked like here: https://www.youtube.com/watch?v=gOPuWi-dbQg We had a very talented web designer and we also built a "Widgets and forms" toolkit. I gave a talk at FrOSCon quite early in the development and it was saved for posterity: https://media.ccc.de/v/c116_lisp_-_2013-08-25_11:15_-_buildi... The first few minutes of audio are broken but it sorts itself out. I built a bunch of things along the way and released as many of them as I could as open source: http://wiki.call-cc.org/users/andyjpb We're currently doing https://registers.app with a similar stack so I'd be pleased to talk more if anyone has any questions. |