问题 I know a lot of reasons for Scala Future to be better. Are there any reasons to use Twitter Future instead? Except the fact Finagle uses it. 回答1: Disclaimer: I worked at Twitter on the Future implementation. A little bit of context, we started our own implementation before Scala had a "good" implementation of Future . Here're the features of Twitter's Future : Some method names are different and Twitter's Future has some new helper methods in the companion. e.g. Just one example: Future.join