Skip to main content

Scala: Lift vs. Play! For Web Development

If you're interested in doing Web development in Scala, have a look at my Stack Overflow question and even more importantly this thread that I started on the Bay Area Scala Enthusiasts mailing list.

In it, there are some choice quotes from David Pollak such as:
In terms of Lift and older browsers, Lift doesn't support them (or at least it doesn't support them well.) At the end of the day, in order to use a Lift app, you need a modern browser (IE 6+, Firefox 1.5+ or WebKit-based [Chrome, Safari])...

Put another way, with 99%+ of the apps people are writing in Lift, they will live in a single JVM...

[When I asked whether a user's session (such as the contents of his shopping cart) was lost when new code was deployed to the server because of the statefulness of Lift, David said] Most of the site deployments that I do in production are during well defined maintenance windows in which the entire service is shut down. I realize that there's a class of services for which that's not acceptable, but the vast majority of sites (the bottom 98% or so) are going to be cool with the maintenance window. If that's not acceptable, there will be a commercial Lift Cluster Manager...

As a practical matter, the deployment and crash scenarios that folks raise are premature optimizations because in the real world, nobody notices (or cares to complain) when Lift sessions stop and are restarted elsewhere.
I'm feeling a little down since I was flamed pretty badly in that thread. Obviously, people in the Python world either like or at least tolerate me a lot more than people in the Scala world.

Anyway, my current plan of action is to learn the Play! framework and Akka. Both look very interesting and very polished. I'm hoping to find a job coding in Scala, but since I've ruled out Lift, my prospects are looking even more slim ;)


Anonymous said…
wow! i'd blow a gasket if someone said as much to me in that context.
Anonymous said…
JJ, 'st ong' comes across as a complete asshole in his post. A large part of evaluating any OSS project or language is discovering the attitudes of the developers and users on the mailing lists. I hope for Scala's sake that 'st ong' is the exception.
- Tavis
jjinux said…
Hey, Tavis, none of my experiences with the Scala world have been very inviting so far. I'm hoping that will change because I really like Scala.
germ├ín said…
That's sad to hear. I have had a very good experience with the Scala community.
Anonymous said…
Anonymous, you need to get off your computer more often, the guys just trying to get some info. I did not see anything in his posts that could be construed as being a "complete asshole".

I myself also want to find out more about Scala/Lift. Does that mean I need to do a poll on people's attitudes before I ask any questisions? And what if the poll says 90% religiously pompous Java/Scala pricks. Does that mean I have to kiss ass to get answers?

Very Lame!

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p