All of my backend work is currently in Scala. I evaluated Lift for a while for my frontend, but I was turned off by it for a few (probably stupid) reasons: 1.

All of my backend work is currently in Scala. I evaluated Lift for a while for my frontend, but I was turned off by it for a few (probably stupid) reasons: 1. The documentation is poor compared to other frameworks, and there's not anywhere near as much collective knowledge around it on the web as with kits like Django or Rails. That isn't entirely bad (you don't have to wade through tons of people who have no idea what they're talking about), but it is frustrating to feel like you're the only one who has ever tried to do something with the code. 2. While they're good about keeping their internal libraries well-factored and independently usable (and I do use a few in other projects), overall, I find the project to be downright overwhelming in its scope. There's just a lot there. They've currently got 131 branches going on github. They implement their own json library, their own actors, their own version of Option, etc, etc. This isn't bad, and for many I'm sure it's actually welcome. For me, though, I value feeling like I 'get' a project, that I understand its scope, what it's providing for me, where it's going, and how to extend it safely myself. I never felt that way with Lift. 3. I don't share their vision on state, or at least the vision they had for a long time. I understand that 2.2 is going to be a lot friendlier for stateless development, though, and that might send me back for another look.