[hythloday]

Twitter's Futures were developed when Scala's Futures weren't tail-recursive (and so not really production-quality). There's probably an item on the roadmap to port Finagle to using scala.concurrent.Future but I doubt it's high priority. The two support the same set of operations in any case - I doubt it'd be a huge problem for a beginner to translate one to the other.

[merb]

Actually a Huge difference is that scala.util.Future takes a implicit ExecutionContext while com.twitter.Future does not.

[hythloday]

It is for production. It's not for a beginner - they should just be using scala.concurrent.ExecutionContext.global.