What is Macker not good for?
Macker is not for class security. Java’s native access modifiers provide guarantees about information visibility and state integrity — private members are guaranteed to be private, unless a class chooses to expose them. Java can do this because “private” is not only enforced by the compiler, but by the JVM itself. Because Macker is not part of the Java language, it can provide no such guarantees. It is a sanity check, not a security check. (You might use Macker as part of a security audit process, but that’s a different question.) Macker is not a substitute for first-class Java language constructs like access control and strong typing. A good object model should use the language to represent and reinforce its architectural intent, Macker or no. Macker is not meant to enforce nit-picky code formatting conventions, and obviously can’t enforce aesthetic standards like “use conceptually clear names”. Finally, Macker isn’t good if you don’t want to specify your own architectural rules. It
