On 3 apr 2010, at 20:36, Simon Hengel wrote:
My point is: we should not try to build one big framework. Instead, I propose that we build a set of smaller libraries that each do one thing very well. Some of these libraries might be designed to work together.
I absolutely agree with that.
I personally think MVC is a perfect fit for the web: model code handles data storage, view code handles HTML/JSON/XML and the controller coordinates between these.
Have you read about the "View First" approach of Lift[1]? While I do not like the monolithic approach of Lift, I really like that specific aspect. I'd not narrow my view on "Rails-Style MVC" right now.
I have not really looked in to it before, the lift documentation always confuses me, but it looks very interesting! I really like the philosophy behind StringTemplate. I think something similar could be done by restricting a view to be |a -> HTML|. Do you think that's enough? Or should there be more restrictions? -chris