David Pollak shows a simple Twitter clone written in Scala. Last night was our first Bainbridge reading group meeting on Programming Erlang, so this is timely, as Scala’s actor libraries are modeled after Erlang. Also of interest is the use of David’s lift web framework for Scala, which includes ideas lifted from Seaside, Django, Rails and Erlyweb.
Archives
- September 2012
- April 2012
- March 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- May 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
Categories
Tags
adobe
apache
apachecon
blogging
books
chandler
community
concurrency
data
dynamic languages
erlang
family
flash
flex
flickr
functional programming
gadgets
internet
iPad
iPhone
java
javascript
languages
leopard
lightroom
Macintosh
microblogging
nikon
open source
osaf
photographs
photography
programming
programming languages
pycon
python
ria
ruby
Seattle
strobist
Sun
tools
twitter
web2.0
WordPress
this is very cool – and I can see it being more deployable in an environment with existing services (being JVM-based.) But you do realize that its strongly-typed don’t you?
In the words of Alan Kay “I’m not against types, but I don’t know of any type systems that aren’t a complete pain, so I still like dynamic typing.” The jury is out on whether Scala’s type system is a complete pain or not.
Dude, I tried to persuade you guys to study Scala earlier this year…
(sorry, I couldn’t resist.) I’m willing to look at Scala next.
As far as typing – I appreciate both approaches – but static typing to me seems to help eliminate a whole class of human errors during development of large systems. Without them, complete coverage of the runtime seems to be required just to rule out simple mistakes. (I see enough JavaScript errors popup on web pages regularly to realize this is a common affliction!)