“[If HApps doesn't do anything...] the project will eventually be superceded by other Haskell frameworks like Turbinado which are not nearly as innovative”
Woohoo! People are talking about Turbinado!
err… Wait! Turbinado is being dissed!
Turbinado vs. HApps
Each project is valid and valuable, so I’m hesitant to get to far into a X vs. Y discussion, but here are some aspects that I thought about when evaluating HApps and developing Turbinado:
- Turbinado is built on top of Nicklas Broberg‘s HSP/HSPR, which I consider to be an innovative-port of ASP to Haskell…
- HApps is a much bigger project with many more features; Turbinado is small and needs your help [shameless plug: help here].
- HApps seems more like a library of really useful functions which is very flexible; Turbinado is more like a web app framework and provides a web server along with defined mechanisms for adding Controller, Views and Components. Convention over Configuration = different styles, not better styles.
- HApps seems less than simple (see here); Turbinado is all about simple (see here)
- HApps has an aversion to relational databases; Turbinado observes that lots of people use relational databases and supports them.
Turbinado vs. HApps, again
To me, it seems as though the choice between HApps and Turbinado depends more on orientation than on functionality. If you are interested in: opposing RDMBSs, but are into something like Sinatra, then HApps is probably the best choice; if you’re interested in writing web apps in the style of Ruby On Rails, then Turbinado (though young and pretty) may be the best choice, especially given the simplicity of building Turbinado (newly cabal installable! to be described in a forthcoming post with tutorials, install details, singing, dancing, high kicks, etc).
Here’s To Success
Most successful languages have more than one web framework, so I hope for success for both HApps and for Turbinado. They’re very different frameworks and serve very different needs. The Haskell community would be well served if both frameworks survived and thrived. As Merb and Rails have demonstrated, cross-pollination is excellent; the stronger HApps and Turbinado are, the more they can benefit each other.