No no, not Java for everything. I know Java, use Java, and don't hate it. Some of the best tooling available (similarly C#, but .NET isn't my thing.) Here's my

No no, not Java for everything. I know Java, use Java, and don't hate it. Some of the best tooling available (similarly C#, but .NET isn't my thing.) Here's my issue: no matter what problem you try to solve the solution looks like Java. I want my solutions to look like my problem. Static imports go part of the way there, and if you're good at naming and architecture, the learning curve for any particular system remains relatively low. It's a hack/sugar, but it helps. But that's about as far as you can go using only stock Java, e.g., no syntax extenders, no byte code treachery, etc. AOP can help, but everyone has to be aware of it, and comfortable with a system designed with AOP from the beginning. Java for shell scripts? No thanks.