Hi, Lift/Scala is getting a lot of attention lately. Having worked with Grails in the past (and finding it quite handy BTW), I'd like to know if there's anyone who has tried both and what's his/her opinion about them. Is one of them better suited for one kind of scenarios whereas the other is better for other kind, or they compete shoulder to shoulder to solve the same problem ?
A:
While this compares a different basket of fruit, I think you may enjoy David Pollak's ("Lift creator") response: http://stackoverflow.com/questions/2683914/why-would-i-use-scala-lift-over-java-spring/3067319#3067319.
One thing to remember about Lift is that it is a continuation-based framework.
pst
2010-06-23 21:50:11
+4
A:
If you're building a CRUD app and you're comfortable with Grails, then stick with it.
If any of the following things are priorities for you, then Lift is going to be better:
- Security -- Lift is more secure than Grails
- Performance -- Lift is faster than Grails because Scala is faster than Groovy
- Ajax -- Lift's Ajax support is simpler and easier than Grails
- Comet -- If you want to build server-push apps, there's nothing better than Lift
- Choice of ORMs -- Lift is not tied to a single ORM, so use anything you want
Net-net, Lift is not another me-too MVC framework. It's something different and something better.
David Pollak
2010-06-28 22:13:53
Thanks for your reply, David. Regarding ORMs, what is the closest approach that can be implemented in Lift that resembles GORM ?
xain
2010-06-28 22:41:01
Lift's Mapper is an ActiveRecord style ORM.
David Pollak
2010-06-29 02:21:37