You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Scala is an expressive language, but the aggregate of its features can yield some of the worst code in existence. Whenever I compare Scala APIs to their Java equivalents, I almost always find the Java version easier to read. And no feature was abused more than implicits.
There's a problem here which is that Java is a language without implicits, so we can read it knowing that all parameters must be explicit. However strict we decide we must be about implicits in Scala, it still permits their usage ("abuse") so we can't reason about it like Java.
It's quite subjective to call dependency injection with implicits "use" or "abuse", but their design was always to model "context". I think DI fits most definitions of "context".
It might be harder to know what all possible readers of some source code might consider part of the context in which they should read it, I don't think the fact it's harder is a good argument for compromising the code's readability by making everything explicit.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
