(In reply to https://twitter.com/gregmcintyre/status/432012568966619137)
Mixins (included Modules) all share one object's state and method set; you need to know everything about every module a class includes or extends before touching it, or risk breaking your code unintentionally. This is practically antithetical to Encapsulation, which hides state behind defined interfaces.
A good quote from a good article:
Using mixins like this is akin to “cleaning” a messy room by dumping the clutter into six separate junk drawers and slamming them shut. Sure, it looks cleaner at the surface, but the junk drawers actually make it harder to identify and implement the decompositions and extractions necessary to clarify the domain model.