m501

I wonder if part of one of these shipments made it to Juarez, the city in Mexico right across from El Paso, TX and not too far from New Mexico. One day a truck full of flattened, new Atari game boxes appeared my street.

All the kids around the neighborhood started taking boxes from the truck and someone figured out you could toss the flat boxes like freesbies. We had tons of fun throwing these boxes around and it didn't occur to me how strange it was to find these empty, new boxes until many years later. I couldn't figure out how this truck-full of boxes was on our street. At the time Juarez was a major manufacturer of electronics and other stuff for the US so, in retrospect, it's possible the boxes actually originated from there.

Play is definitely more akin to django than lift is. Lift, as I've read not experienced, has specific philosophy for how to build web apps that is slightly different than django or play.

I'm a long time django user. I love django. I've used it in production apps. I like to try out new languages as a hobby and so I got myself the programming in scala and the Play framework in action (manning). Just trying out Play however I can't seem to get this feeling that I could do it more easily and faster in django, though that may be because I'm comfortable with django and python. There are also a ton of django apps that I can leverage to build out parts of my app. I'm not sure about the play ecosystem in that respect.

I'm also specifically looking for advantages that the language itself can bring but since I haven't gotten very far I haven't discovered any yet but I'm hopeful that I will be pleasantly surprised.

Having said all that I just saw some play love coming from LinkedIn: http://engineering.linkedin.com/play/play-framework-linkedin