<div class="gmail_quote"><div>gitit [1] is happstack based and is very impressive -- you may want to read its code to see how you can build web applications using happstack (not *on*, for gitit).</div><div><br></div><div>[1] <a href="http://gitit.net/">http://gitit.net/</a></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="gmail_quote"><div><div></div><div class="h5">
On Tue, Mar 23, 2010 at 7:05 PM, Ozgun Ataman <span dir="ltr"><<a href="mailto:ozataman@gmail.com" target="_blank">ozataman@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5">
<div style="word-wrap:break-word">Greetings all.<div><br></div><div>I have been for quite some time trying to assess the feasibility of using Haskell in relatively large, high volume, high availability, long-running web application projects. I have enjoyed learning and using Haskell very much for the past year and I often find myself missing various language features when reasoning about alternatives like Ruby (on Rails). If I can identify the right set of tools for the job, I would really like to take the plunge and make Haskell my standard go-to language in web applications.</div>
<div><br></div><div>Here are the couple of key questions that I wanted get your feedback on:</div><div><br></div><div><ol><li>Do you consider Haskell and its environment of libraries ready for prime time in web app development as defined above?</li>
<li>What collection of libraries would you use in such an effort?</li><li>What are the up and coming packages/technologies in Haskell-land you would watch out for?</li></ol></div><div><br></div><div>Also, here are some core requirements that I would define for such a project:</div>
<div><br></div><div><ul><li>Ease/speed of development in both back and front-ends, minimal boilerplate</li><li>Extendability and flexibility in iterative development</li><li>Robustness and reliability in production environment</li>
<li>High performance</li><li>Scalability</li><li>Ability to interface with new technologies in the future: Cassandra, Redis, memcached, etc.</li><li>Ease of implementing common/reusable features across web applications: user authentication, S3 file uploads, thumbnail/image handling, exception notifications, etc.</li>
</ul><div><br></div><div>In terms of libraries, I can think of a few key components (as pointed out by several others before) that one would need to arrange:</div><div><br></div><div><ul><li>Choice of server (happstack vs. alternatives)</li>
<li>Templating (xhtml vs. file templates vs. newer efforts like BlazeHtml)</li><li>Data/storage layer: HDBC vs. HaskellDB vs. others</li></ul></div><div><br></div><div>I know this is a common topic in Haskell-Cafe, but I have failed to identify conclusive opinions from experienced Haskellers out there in previous discussions. My apologies in advance if this is a blatantly redundant post.</div>
<div><br></div><div>All the best,</div><div>Ozgun</div><font color="#888888"><div><br></div></font></div></div><br></div></div>_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Alp Mestanogullari<br><a href="http://alpmestan.wordpress.com/">http://alpmestan.wordpress.com/</a><br><a href="http://alp.developpez.com/">http://alp.developpez.com/</a><br>