Most Read Latest News Blog Resources
Digg!  Digg
Reddit  Reddit


            iphoneapp GET THE APP!

Lift Framework brings Scala to Web




January 28, 2010 —  As the Scala functional programming language goes from version 2.7.4 to 2.8, the Lift Framework will update to version 2.0 to bring developers many of Scala’s benefits, including a development model that looks like Ruby on Rails.

David Pollak, creator of the Lift Framework, said he originally created Lift after using Ruby on Rails in 2004. When he first used Rails, he said, “I realized I was missing a lot of things from Java land—for example, a stable runtime and the ability to scale on a single box.” But Pollak didn't want to go back to using Java's numerous third-party Web frameworks.

Instead, Pollak began searching for a better language to use on top of Java. He found Scala and discovered that it offered many of the benefits he was looking for, but lacked the Web frameworks that are so common in Java. In December of 2006, Pollak wrote the first lines of the Lift Framework, and by February 2007, it was a full-fledged open-source project with multiple contributors.

There are many benefits to using Lift, said Pollak. One of the biggest draws is the security model built into Lift. Pollak used to be CTO of Cenzic, a Web application security company, and he says he learned a lot of tricks to help make Lift safer to use than normal frameworks.

For one thing, cross-site scripting vulnerabilities don't happen by accident when writing to Lift. Pollak also said that each session created in Lift has an automatically generated unique ID, which can make man-in-the-middle attacks much more difficult to execute against a Lift-based Web application.

“We try to make sure the default ways Lift applications are coded are secure and that the developer has to do something to introduce vulnerabilities,” said Pollak.

Lift is currently in use at Google-owned startup Foursquare and at Xerox. Pollak said that future work on the framework will be focused on making things easier to deal with over time. He said that Scala 2.8 will be a major overhaul of that language.

Version 2.0 of the Lift Framework will take advantage of many of the improvements in Scala. For one thing, developers will be able to assign Web page renderings to be done across multiple threads, which speeds up response time from the server and allows for Web servers to scale across a cluster, said Pollak.

Why use Lift instead of Wicket or JavaServer Faces and JavaServer Pages? Because, said Pollak, using those Java Web systems will increase the size of your code by three to four times.

Additionally, he said, “Even with JSF and a lot of the Java frameworks, what you wind up with is everything is an object, and you have to cast it into what you want, whereas in Lift it's very type safe."


Related Search Term(s): Java, Lift, Scala


Share this link: http://www.sdtimes.com/link/34090
 

Comments

02/12/2010 11:55:17 AM EST

Lift and Scala are both excellent technologies, but I don't believe that Google owns Foursquare. Foursquare seems to be the successor of Dodgeball, which was purchased by Google and then shut down.

United StatesSteven Merrill


02/15/2010 07:44:06 AM EST

With all due respect to Mr. Pollack and his innovative Lift framework, JSF is very typesafe. Saying that JSF is a framework where "everything is an Object" is to an entire phase of the JSF lifecycle, which is explicitly devoted to type safety. Ed Burns JSF spec co-lead.

United StatesEd Burns


05/27/2010 11:40:23 AM EST

The simple fact of the matter is that Scala generics are better specified and more useful than Java's. After all, Scala's type system was designed by the inventor of Java generics, with much benefit of hindsight. It fixes many of the problems in Java's system. Declaration-site variance works better than use-site variance. Things like abstract types have no equivalent in Java and definitely enable the use of generics for use cases where generics aren't a practical solution in Java. With Java, one is are sometimes faced with a choice between adding unwanted, nonsensical type parameters to a method and just giving up on generics. In Scala, one need not make that choice. I would say that Pollak's statement was fair in a sense, but it's more of a Scala versus Java issue than a Lift versus JSF issue.

United StatesNathan Bryant


Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading



 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 8/1/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Like Ruby n' Rails
Programming languages and Web frameworks go together like peas n carrots. Or Ruby n' Rails.
07/30/2010 04:36 PM EST

Adobe buys a Web-based IDE
Adobe looks to buy a rapid and agile Web development environment.
07/28/2010 03:49 PM EST

OpenStack opens up
OpenStack looks to be an intriguing new idea for running clouds.
07/28/2010 01:56 PM EST

 

Events calendar tab
8/1/2010 to 8/5/2010
Boston
SHARE

8/2/2010 to 8/6/2010
Redmond, Wash.
1105 Media

8/9/2010 to 8/13/2010
Orlando
Agile Alliance

8/23/2010 to 8/26/2010
San Jose
S&S Media

8/30/2010 to 9/2/2010
San Francisco
VMware