51–60 of 79 posts
Is supergluing your framework to the dom really a feature?
If you want to have your dom events be handled server-side, then it is. It also lets you do things like have a dom node be bound to the state of a server-side object so the dom contents are updated when the server-side object's contents are changed -- it just takes care of the plumbing for you.
Earlier quoted context omitted.
I think that the author is coming from the Java world, in which case the comparison he likely had in mind is not Rails or django, but the plethora of Java web frameworks. Personally, for Java Web Frameworks there are two I like, for quite different reasons. The first is Spring MVC. the rest of Spring can go die in a fire for all I care, but the Spring MVC part is quite nice. Used properly it allows you to very quickl…
Naive question here (I've worked on web apps, but it was using Java technology of the circa 2000 vintage, so my knowledge is quite limited). It seems to me that it would be really nice for a developer to be able to treat html/javascript/css similar to the way that developers today treat assembler - a very low-level way to the browser to do exactly what you want, but something that the large majority of programmers do…
What's not mentioned (it's hard to sell) is, 50%+ of the reason Lift is so fabulous is, you're writing Scala. It's a mighty upgrade in quality of life, from either Ruby, Java or Python. By corollary, what's being omitted is, the learning curve is steep. Scala isn't super-easy, and Lift dives fairly deep into the more complex stuff - implicits, currying, etc. Nor is Lift itself all too well documented just yet. Yes, t…
What's not mentioned (it's hard to sell) is, 50%+ of the reason Lift is so fabulous is, you're writing Scala. It's a mighty upgrade in quality of life, from either Ruby, Java or Python. By corollary, what's being omitted is, the learning curve is steep. Scala isn't super-easy, and Lift dives fairly deep into the more complex stuff - implicits, currying, etc. Nor is Lift itself all too well documented just yet. Yes, t…
Two books on Lift? All I know about is the Apress book, which significantly lowered my opinion of Apress. What's the other?
Exploring Lift: http://exploring.liftweb.net/
Lift in Action MEAP: http://www.manning.com/perrett/
Earlier quoted context omitted.
I think that the author is coming from the Java world, in which case the comparison he likely had in mind is not Rails or django, but the plethora of Java web frameworks. Personally, for Java Web Frameworks there are two I like, for quite different reasons. The first is Spring MVC. the rest of Spring can go die in a fire for all I care, but the Spring MVC part is quite nice. Used properly it allows you to very quickl…
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.
Earlier quoted context omitted.
Two books on Lift? All I know about is the Apress book, which significantly lowered my opinion of Apress. What's the other?
A couple possible matches: Exploring Lift: http://exploring.liftweb.net/ Lift in Action MEAP: http://www.manning.com/perrett/
Hm. Lift even works on Google App Engine. Pretty nice: http://www.scala-lang.org/node/1826 That would take the pain out of deploying an app.
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…
3. Ajax support seems pretty common but Comet seems pretty rare. Most major Javascript libs seem to have little or no support for Comet. Also, server side support for Comet seems even rarer. 4. Declarative syntax for dependencies seems much simpler than imperatively updating dependencies in Javascript 5. This one isn't presented very well. Essentially, all server side presentation logic is done in Scala code rather t…
shadowfiend Person Name Hometown, ST
class Users { lazy val users = User.findAll() def userList = { ".user" #> users.map { user => ".username" #> user.username & ".name " #> user.name & ".hometown " #> (user.hometown + ", " + user.state) } } }
Earlier quoted context omitted.
If you want to have your dom events be handled server-side, then it is. It also lets you do things like have a dom node be bound to the state of a server-side object so the dom contents are updated when the server-side object's contents are changed -- it just takes care of the plumbing for you.
How well does Lift work if you want your applications to still work with JavaScript disabled?
Just out of curiosity can you highlight the advantages lift has over other modern frameworks such as rails or django (and maybe some of the php frameworks). Most (or all) of the 7 things ship with rails 3. Stacking them up against one another might yield a better comparison.