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
Using implicits for DI is bad b/c reading code requires more context. It's why the Linux kernel has never adopted C++, b/c kernel devs want to reason about pieces of code in isolation, C making everything explicit. Reading code is more important than writing it, always.
But shouldn't that be what context is? It's the things that the reader can take for granted, and every additional explicit parameter that ought to be taken for granted instead has to be present, diluting the parameters that are actually significant to the method.
Reading code is more than being able to reason about fragments of it in isolation. That's important, of course, but unnecessary explicit parameters can also look a lot like boilerplate.
Seeing that a method interacts w/ the database, or can potentially fire missiles, is as important at the call-site, as its definition. And if we want context, if we want DI, Scala also has a true and tried way of doing it, which is OOP classes, closures on steroids.
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.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
