Why I'm Moving Away from the Play Framework

Post by notJim » Sat, Mar 10, 2012, 2:06 AM UTC

SkyMarshal wrote: post #72

djb_hackernews wrote: post #21

Earlier quoted context omitted.

I use Play! for my hobby projects and Lift for work. Coming from MVC lift is very bizarre. Having html and javascript inside my scala classes gives me a queasy feeling. I also think Lift is dead. The creator of the project left, the documentation isn't great, View first model isn't popular, very little activity in #lift, very little activity in the lift framework google group. Not good signs.

> Having html and javascript inside my scala classes gives me a queasy feeling. Yeah that's an interesting tradeoff. I like it because it helps keep code completely out of the html templates, which is a design goal of lift. I tend to work with designers who do HTML/CSS only, not javascript, and I do the backend Scala and frontend Javascript, so that separation of roles works. But if your dev team (as most big ones do…

Post by eta_carinae » Sat, Mar 10, 2012, 7:20 AM UTC

cletus wrote: post #37

I've recently been in the market for a Java Web framework and have settled on Play. There are a lot of things I really like about it. I have no problem with the Play developers going "off the reservation" (as far as JEE goes). I'm finding some things are a bit awkward, particularly around templates and routing. Also, the documentation while good is lacking in other parts. Play is a very prescriptive framework but onl…

Post by thebluesky » Sat, Mar 10, 2012, 9:43 AM UTC

eta_carinae wrote: post #83

cletus wrote: post #37

I've recently been in the market for a Java Web framework and have settled on Play. There are a lot of things I really like about it. I have no problem with the Play developers going "off the reservation" (as far as JEE goes). I'm finding some things are a bit awkward, particularly around templates and routing. Also, the documentation while good is lacking in other parts. Play is a very prescriptive framework but onl…

Good analysis. I like Play overall but two things concern me, both related: 1) they are moving toward Scala and 2) they are adopting sbt. This looks to me more like a "picking a shiny toy" move than something that is being done to benefit users (Scala is still quite a marginal language and sbt is very controversial, even among Scala enthusiasts).

Post by hythloday » Sat, Mar 10, 2012, 7:45 PM UTC

runT1ME wrote: post #79

hythloday wrote: post #54

Earlier quoted context omitted.

Just FYI, ConcurrentHashMap is indeed lockfree (although it's got a gargantuan memory footprint). Wrapping your HashMap with Collections.synchronizedMap gives you a blocking threadsafe HashMap.

ConcurrentHashMap is not lock free, it uses lock striping across multiple buckets.