> It intentionally avoids putting code in the template. This keeps the template > clean... Putting code inside the template is one of the worse design > decisions ever. Putting template fragments inside Scala code makes tremendous > sense as it allows a truly flexible way of achieving compositionality, > reusability etc.
I think Lift does not win anything over Rails at this point. In Rails, putting code inside template is also a really very bad practice. That's why Rails has "app/helpers" directory, code should be put in helpers and refactored there. What I mean is when advertising Lift over Rails, this should not be insisted much, e.g. saying Rails puts code inside the template, or experienced Rails developers would think Lift developers don't know Rails enough. Instead of that, I think one of Lift features that is absolutely a big win is seamless request-response cycle. One consequence is that it makes building Ajax/Comet application very easy. Nitrogen framework also has this feature. That's why I put the link to its home page, with the hope that Lift committers would glance its implementation. Maybe there's something there they may learn from, I don't know. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
