4 ms·

Lift is hands-down the best web framework available today... Can someone a little less involved please comment on the validity of this and the claims that foll

Lift is hands-down the best web framework available today... Can someone a little less involved please comment on the validity of this and the claims that follow it? Is it something I should be checking out?

vladev 16y ago
I've tried using it a few months ago. It's quite hard actually. The docs were poor, understanding the concepts was not easy and in a lot of places it abuses the Scala syntax: LiftRules.rewrite.append { case RewriteRequest(ParsePath(List("shopInfo", "view", id), _, _, _), _, _) => RewriteResponse("shopInfo" :: "view" :: Nil, Map("id" -> id)) My opinion is that I don't like. At all! There are better and simpler ways to do things, even the real-time chats they brag about (socket.io, anyone?).
- KirinDave 16y ago
  One of the things I asked dpp for was a real introduction. He's very excited to talk about Lift's comet stuff (and it's easily the best comet impl you can ask for), but in the process he sort of leaves people who just wanted to get "hello world" up on the browser behind. He's doing a round of lift classes, so hopefully some of that material will migrate to the website and make lift more approachable.
  - sorenbs 16y ago
    The video from the first Lift training is available here: http://vimeo.com/groups/75631/videos http://vimeo.com/groups/75631/videos (skip the first 14 mins). It covers what you need to get started with Lift.
    - KirinDave 16y ago
      That's great, and the content seems good, but I still feel like a 2-hour video is sort of a glib response to "there is no good introduction to the framework!" :)
    - deleted 16y ago
      [deleted]
noelwelsh 16y ago
It is pretty good. Is it the best? I couldn't say. Some misc. good points: - It runs on the JVM, so you get performance and libraries, but you don't need to go through all the Java BS to get something working. (Seriously, performance is overlooked. If performance is not an issue, why did Facebook write HipHop?) - Comet support (via Actors) is great and really easy to use. Ajax as well. Writing interactive website is very easy. - The "no plumbing" approach is pretty good. You don't have to setup routes of anything (mostly). You just embed callbacks directly in the page in a lot of cases and things just work. - Templates are nice. The bad points: - The ORM situation isn't great. - The documentation is terrible (but improving). Overall Lift is certainly worth looking at for some good ideas. Having a concise language and simple toolkit on the JVM is great.
- LiveTheDream 16y ago
  > If performance is not an issue, why did Facebook write HipHop? Energy. Facebook has thousands of servers running PHP code. HipHop allows them to have the same performance with half the servers[1]. 50% less servers at that scale equates to non-trivial energy (and cost) savings. [1] http://developers.facebook.com/blog/post/358 http://developers.facebook.com/blog/post/358
cageface 16y ago
It's not nearly enough of an improvement over Rails or Django to displace them. I expect it to do much better over the next few years than any other functional programming framework but I don't expect it to escape that niche. Pollak has realized, as I begrudgingly did, that Scala, like all the other type-inferencing static FP langs, is just too hard for the programming mainstream. Once you've decided to go polyglot you might as well just use a boring but safe core language like Java or C++ and build as much on top of that as you can in your dynamic language of choice.
sorenbs 16y ago
If you have a small team of above-average developers and truly commit yourself to learning "the lift way", including all the power of scala, I believe Lift will get you very far. https://groups.google.com/forum/#!topic/liftweb/ViklDFsBtPo https://groups.google.com/forum/#!topic/liftweb/ViklDFsBtPo quote: "Our experience with Lift was the best possible, and an important part of that was having Scala available within the framework. No other language could have allowed us to do what we did within such a short time frame, Ruby included."

vladev 16y ago

I've tried using it a few months ago. It's quite hard actually. The docs were poor, understanding the concepts was not easy and in a lot of places it abuses the Scala syntax: LiftRules.rewrite.append { case RewriteRequest(ParsePath(List("shopInfo", "view", id), _, _, _), _, _) => RewriteResponse("shopInfo" :: "view" :: Nil, Map("id" -> id)) My opinion is that I don't like. At all! There are better and simpler ways to do things, even the real-time chats they brag about (socket.io, anyone?).

KirinDave 16y ago
One of the things I asked dpp for was a real introduction. He's very excited to talk about Lift's comet stuff (and it's easily the best comet impl you can ask for), but in the process he sort of leaves people who just wanted to get "hello world" up on the browser behind. He's doing a round of lift classes, so hopefully some of that material will migrate to the website and make lift more approachable.
- sorenbs 16y ago
  The video from the first Lift training is available here: http://vimeo.com/groups/75631/videos http://vimeo.com/groups/75631/videos (skip the first 14 mins). It covers what you need to get started with Lift.
  - KirinDave 16y ago
    That's great, and the content seems good, but I still feel like a 2-hour video is sort of a glib response to "there is no good introduction to the framework!" :)
  - deleted 16y ago
    [deleted]

noelwelsh 16y ago

It is pretty good. Is it the best? I couldn't say. Some misc. good points: - It runs on the JVM, so you get performance and libraries, but you don't need to go through all the Java BS to get something working. (Seriously, performance is overlooked. If performance is not an issue, why did Facebook write HipHop?) - Comet support (via Actors) is great and really easy to use. Ajax as well. Writing interactive website is very easy. - The "no plumbing" approach is pretty good. You don't have to setup routes of anything (mostly). You just embed callbacks directly in the page in a lot of cases and things just work. - Templates are nice. The bad points: - The ORM situation isn't great. - The documentation is terrible (but improving). Overall Lift is certainly worth looking at for some good ideas. Having a concise language and simple toolkit on the JVM is great.

LiveTheDream 16y ago
> If performance is not an issue, why did Facebook write HipHop? Energy. Facebook has thousands of servers running PHP code. HipHop allows them to have the same performance with half the servers[1]. 50% less servers at that scale equates to non-trivial energy (and cost) savings. [1] http://developers.facebook.com/blog/post/358 http://developers.facebook.com/blog/post/358

cageface 16y ago

It's not nearly enough of an improvement over Rails or Django to displace them. I expect it to do much better over the next few years than any other functional programming framework but I don't expect it to escape that niche. Pollak has realized, as I begrudgingly did, that Scala, like all the other type-inferencing static FP langs, is just too hard for the programming mainstream. Once you've decided to go polyglot you might as well just use a boring but safe core language like Java or C++ and build as much on top of that as you can in your dynamic language of choice.

sorenbs 16y ago

If you have a small team of above-average developers and truly commit yourself to learning "the lift way", including all the power of scala, I believe Lift will get you very far. https://groups.google.com/forum/#!topic/liftweb/ViklDFsBtPo https://groups.google.com/forum/#!topic/liftweb/ViklDFsBtPo quote: "Our experience with Lift was the best possible, and an important part of that was having Scala available within the framework. No other language could have allowed us to do what we did within such a short time frame, Ruby included."