Lift and Play! embody very different philosophies of web development, but if you want something closer to the common MVC frameworks Play! is very nicely done.
Well if you mean Model/Controller/Route first vs View first, yes they are philosophically different. But I meant more along the lines of how friendly the API is. An additional example would also include the fact that although Lift has come a long way in providing meaningful error information, by contrast Play!'s take on it is just a breath of fresh air. This isn't to say that Lift is doing it wrong; it's error messaging is less arcane than some other web frameworks.
I agree that Play shows a lot of polish and attention to detail. I haven't done anything significant with it but it was very pleasant for the few simple things I tried.
Comments
Lift and Play! embody very different philosophies of web development, but if you want something closer to the common MVC frameworks Play! is very nicely done.
Well if you mean Model/Controller/Route first vs View first, yes they are philosophically different. But I meant more along the lines of how friendly the API is. An additional example would also include the fact that although Lift has come a long way in providing meaningful error information, by contrast Play!'s take on it is just a breath of fresh air. This isn't to say that Lift is doing it wrong; it's error messaging is less arcane than some other web frameworks.
I agree that Play shows a lot of polish and attention to detail. I haven't done anything significant with it but it was very pleasant for the few simple things I tried.