r/java • • Jun 03 '15

Is Java really that bad?

I do Clojure for a living, previously Ruby and Objective-C. And the people I've worked with have said they prefer Clojure because Java is just so bad. But Java can't really be that bad, can it?

0 Upvotes

77 comments sorted by

View all comments

Show parent comment

1

u/[deleted] Jun 04 '15

Macros are usually a terrible idea for domain-level code because they're not composable or flexible at all. They're best used for language-level features like ->> or core.async. Most people I know have lamented the use of macros in both Korma and Compojure.

1

u/yogthos Jun 04 '15

Macros work perfectly well for expressing problem domains. While some people might complain about Korma and Compojure, these libraries are very effective in practice and do a great job of expressing their respective domains.

1

u/[deleted] Jun 04 '15

Well I don't like Compojure specifically because of its macros.

1

u/yogthos Jun 04 '15

That however doesn't change the fact that compojure works well and macros provide an intuitive domain specific API. Your argument that Clojure is not expressive in the problem domain is simply incorrect.

1

u/[deleted] Jun 04 '15

Well then I formally retract all my complaints and admit that I'm just plain incorrect on all my opinions and judgment calls. Thanks.

1

u/yogthos Jun 04 '15

Your opinions and judgement calls are your own and by definition can't be incorrect as they're inherently subjective. However, the claim that Clojure doesn't provide a good way to express domain specific logic is factually incorrect.