If you don't like DI or AOP, then you can just code plain Java. If you like DI but not AOP, then something like Guice or plain Java and some self-discipline wo

If you don't like DI or AOP, then you can just code plain Java. If you like DI but not AOP, then something like Guice or plain Java and some self-discipline would probably work better for you. If you like DI and AOP, then you can let Spring get you as close to proper AOP as Java allows without weaving, or you can use the same syntax to do compile-time weaving to get a non-leaky abstraction All these are just choices to make; it seems like you're more fighting against the fact that you don't like how the 'industry' is making these 'enterprise standard' choices for you. On a technical level it's more like criticising Rails for using meta-programming everywhere, or C because it's so low-level (i.e. that's what they were designed for! If that's not what you need, don't use it!)