Simon, <div><br></div><div>I posted the following to the mailing list yesterday but it has been awaiting moderation since then and I would like to contribute something to the conversation </div><div><br></div><div><a href="https://gist.github.com/118dc4cd9d8223c33f63">https://gist.github.com/118dc4cd9d8223c33f63</a></div>
<div><br></div><div><a href="https://gist.github.com/118dc4cd9d8223c33f63"></a>I hope reading it at that link isn't too troublesome.</div><div><br></div><div>Best</div><div><br></div><div>John<br><br><div class="gmail_quote">
On Sat, Apr 3, 2010 at 11:36 AM, Simon Hengel <span dir="ltr"><<a href="mailto:simon.hengel@wiktory.org" target="_blank">simon.hengel@wiktory.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> My point is: we should not try to build one big framework. Instead, I<br>
> propose that we build a set of smaller libraries that each do one<br>
> thing very well. Some of these libraries might be designed to work<br>
> together.<br>
<br>
I absolutely agree with that.<br>
<br>
> I personally think MVC is a perfect fit for the web: model code<br>
> handles data storage, view code handles HTML/JSON/XML and the<br>
> controller coordinates between these.<br>
<br>
Have you read about the "View First" approach of Lift[1]? While I do not<br>
like the monolithic approach of Lift, I really like that specific<br>
aspect. I'd not narrow my view on "Rails-Style MVC" right now.<br>
<br>
Cheers,<br>
Simon<br>
<br>
[1] <a href="http://wiki.liftweb.net/index.php?title=Lift_View_First" target="_blank">http://wiki.liftweb.net/index.php?title=Lift_View_First</a><br>
_______________________________________________<br>
web-devel mailing list<br>
<a href="mailto:web-devel@haskell.org" target="_blank">web-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
</blockquote></div><br></div>