News for hackers. Stuff that matters.
Re:Why moving to Scala - Part I - Writing less code by icey on Tuesday June 21, 2011 @11:55AM (#2679266)
I can't wait to see some case studies about experiences with Scala over the term of a long-lived, large project.

I like the language, but sometimes it feels like it promotes a lot of "creative" coding. My concern is that the idioms for dealing with things like collections seem to change with some frequency as more and more features get added to the language.

It's possible that my concerns are misplaced, I've written < 10,000 lines of Scala so I'm certainly a neophyte. It's just been troubling to find so many suggestions for doing things like folding/reducing.

Re:Why moving to Scala - Part I - Writing less code by harryh on Tuesday June 21, 2011 @12:12PM (#2679310)
FWIW we've got about 150k lines of scala code in the foursquare codebase and are thusfar very happy with it. There are certainly ways of writing bad code in scala (as with any language) but you learn pretty quickly how to avoid them.
Re:Why moving to Scala - Part I - Writing less code by icey on Tuesday June 21, 2011 @12:21PM (#2679330)
Do you feel that you would have had as much success with less strong developers? (Edit: probably better phrased as "Do you think success would have been possible with less strong developers")

I don't mean "bad" developers as much as I mean ordinary "enterprise" developers.

The real concern I have is with hiring - what is the likelihood that you can take a competent Java developer (or any competent developer, I suppose) and expect them to make good decisions with Scala in a relatively short window of time (say 1-2 months)?

Re:Why moving to Scala - Part I - Writing less code by harryh on Tuesday June 21, 2011 @12:33PM (#2679362)
It's hard for me to say definitively because the eng team at foursquare is AWESOME (I know I"m biased here, but I really do think it's exceptional).

I do think it would have been possible though. In a lot of ways scala is a combination of the benefits of a compiled/type checked language (which should make things easier for developers of any skill level) + the concision of an interpreted language like python or ruby.

Re:Why moving to Scala - Part I - Writing less code by icey on Tuesday June 21, 2011 @12:36PM (#2679378)
Thanks a lot for taking the time to answer, Harry. I really enjoyed the recording of your talk about Lift from the New York Scala meetup, by the way.
Re:Why moving to Scala - Part I - Writing less code by lylejohnson on Tuesday June 21, 2011 @01:50PM (#2679685)
For those of us who'd like to add this to our Squrl queues to watch later, the video is here:

http://www.vimeo.com/8057986

and the slide deck is here:

https://docs.google.com/present/view?id=dcbpz3ck_24f3v83ggz&...

Re:Why moving to Scala - Part I - Writing less code by harryh on Tuesday June 21, 2011 @01:25PM (#2679592)
Happy to help out. FYI you can check out our eng blog at http://engineering.foursquare.com to see other posts about the technical details of foursquare.
Re:Why moving to Scala - Part I - Writing less code by meowzero on Tuesday June 21, 2011 @01:50PM (#2679688)
We use Scala at our company too (The Weather Channel) and as long as you get a competent developer and a good mentor, they can write decent Scala code quick.