The best Web Framework - what makes Lift different

Post by zem » Sat, Jan 22, 2011, 5:59 PM UTC

aaronblohowiak wrote: post #38

Pewpewarrows wrote: post #15

1. Fetching content with AJAX and placing it into the DOM is "supported" by every web framework in existence. 2. Proxying ads through your own backend that threads itself? Yawn. 3. AJAX and COMET have pretty standard support. Again, this is left up to you with your Javascript library of choice. 4. Again, this is Javascript work. It might save me a little bit of development time, but I'd much rather be in complete con…

1. Lift goes further in enabling convention over configuration for common AJAX tasks that are part of normal workflows, so there is less boilerplate to write. 2. Parallel rendering means you can move to a SOA where different components on the UI are served by different backend services. This can be great if you have a recommendation service, a shopping cart and main content areas that are all served by different syst…

Post by steele » Sat, Jan 22, 2011, 8:06 PM UTC

nickbarnwell wrote: post #55

steele wrote: post #32

Earlier quoted context omitted.

Dave Pollak has worked in Rails for a long time. JRuby support is on the way for lift too. shrug If Java is a necessity, Play! is a breath of fresh air.

In my very humble (and inexperienced) opinion, Play! is the closest you're going to get to the development speed of Rails or Django and their ilk while still using Java.I recently finished writing a small app in it for a school project, and it was nothing but enjoyable. Not in love with the templating, but everything else was a joy.

Post by [deleted] » Sat, Jan 22, 2011, 8:07 PM UTC

aaronblohowiak wrote: post #39

steele wrote: post #33

Lift is good, and if you're doing webapps in scala, you're probably going to use a lift package _somewhere_. My impression of Lift is that the API aren't self-explanatory at first glance. import SHtml and S, hmmm, I know they do different things but I have to be reminded of what exactly from those packages I need. I'm surprised no one has mentioned stateful vs stateless and horizontal scaling, yet. These are concerns…

Yea, we're working on the docs. Session affinity using the session id works pretty well. Many of the features come from the ability to have actors that propagate their state up to clients.

Post by [deleted] » Sun, Jan 23, 2011, 8:25 PM UTC

mgkimsal wrote: post #17

wavewash wrote: post #14

On the multi-page form demo. It goes automatically from page 1 to page 3. I expected a page 2.

If the age entered is < 18 it goes to page 2 - read the code.

Post by itsnotvalid » Tue, Jan 25, 2011, 12:17 PM UTC

bad_user wrote: post #24

jasonkester wrote: post #4

Looks like it's great for building the things the authors thought you might want to build. Just like every other "SuperMagic" framework, I suspect there's a lot of pain to be had once you step just a little outside of what it expects you to do with it. We've all re-written Django inside of Django at least once, and thus have been burned by this sort of thing before. Personally, I think I'll wait to see some big proje…

I've been using Django for a lot of projects, but have recently converted to Rails 3 for a personal project. What I like about Rails is that plugins are mostly pieces of infrastructure, not ready-to-use mini-applications that are hard to customize. And Rack plugins (pieces of middleware, done in a standard/reusable way, contrary to Django's middleware) are just awesome. I also like about Rails that authentication and…