Hi there! I fell in love with newLISP a few years ago, mostly for its clean documentation, the fact that everything seemed to make sense, and the fact that it

Hi there! I fell in love with newLISP a few years ago, mostly for its clean documentation, the fact that everything seemed to make sense, and the fact that it was small and fast. I found the newLISP web framework Dragonfly and adopted it to build a prototype website for my previous company. I used Solr for the document storage engine, and used newlisp's excellent native XML conversion to convert an ugly XML feed into a newLISP list and then into individual Solr documents. Then I used Dragonfly to write a front-end searching application that was launched to a select group of our customers. newLISP made it really easy to prototype rapidly and deliver new features quickly. Dragonfly stopped being updated, so I decided I wanted to make my own web framework. That became newLISP on Rockets (www.newlisponrockets.com) and I released the source on GitHub. Although I haven't updated the newLISP on Rockets website much lately, it's mostly because I'm too busy using Rockets in my current job. I built a searching application for all our documentation, and now I'm busy building business intelligence stuff. It's nothing too fancy, and I don't consider myself a great programmer at all. But I love the fact that newLISP allowed me to make all these things quickly and with few lines of code, and it's easy for me to maintain them afterwards. That's the true value that newLISP has for me.