I should also have included this article discussing (generally) the
merits of IoC in Scala.
http://moreindirection.blogspot.com/2011/08/implicit-environment-patt...
It could perhaps be another topic of discussion - I know there are a
lot of Spring fans. I take the point about bulky 3rd party libs,
programming in XML, and can see that declaring an implicit
'environment' could be useful; It declares a dependency on other
systems in your method/class signature, but making it implicit makes
it feel natural. I'd like to try it with logging... often we forgive
service lookup/singleton pattern with loggers, but if the logger is
part of your environment, then it may be a less intrusive way to test/
assert some internals from unit tests without having to change your
production code (I've seen some people cringe at relaxing a private
helper method to package scope to make it testable).
Anyway, just a bit of thought food.
