<div class="gmail_quote">On 17 June 2011 14:53, Michael Snoyman <span dir="ltr"><<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>></span> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm not saying Happstack or Snap are bad frameworks, quite the<br>
opposite. But I don't think these generic "X isn't mature" or "Y has<br>
bad documentation" do much to help newcomers become acclimated.<br></blockquote><div><br></div><div>I'll back this up, Yesod has quite an extensive book with tips and tricks including corner cases and such: <a href="http://www.yesodweb.com/book">http://www.yesodweb.com/book</a></div>
<div><br></div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
I'd like to respectfully disagree with this assessment. I'm not quite<br>sure what you mean by "mature", but Yesod has been developed actively<br>for two years, has the vast majority of features you'll need on a<br>
project, is in use by many production settings and has the highest<br>performance figures of any of the big three frameworks.</blockquote><div><br></div><div>FWIW I think he means the API changes, not that the software itself is runtime-stable. The "developed actively" may imply a changing API. I don't know whether this is true, but I think that's what he meant.</div>
<div><br></div><div>Anyway, I doubt maturity as in runtime stability matters that much to newbies.</div></div>