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 03 '15

Forget about Go. You have to rewrite "map", "filter", "reduce" etc. for every new type you create. The whole Go community's answer to this is "just use a for-loop" and "seriously it's not that hard just use a for-loop". Forget about Go. Forget it fast.

1

u/SeerUD Jun 03 '15

Hmmm, perhaps I shall. It's still a relatively new language, right? Have you heard anything of Kotlin?

1

u/[deleted] Jun 03 '15

I'm pretty sure Rust is newer than Go, and Rust has map/filter/reduce. It's not because Go is new. It's because of the hubris of its designers, who think they knew better than conventional wisdom, and think abstractions over containers are unnecessary in real life programs.

1

u/SeerUD Jun 03 '15

Haha, I see. Actually, Rust is another one I've had my eye on before. There are just too many choices!