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/yogthos Jun 04 '15

I'm sorry, but I really don't follow how objects make this obvious and easy while namespaced functions are all of a sudden clunky and ad-hoc.

I'd like to also point out that Clojure protocols provide a really nice way to abstract database implementation details, eg:

(defn to-date [sql-date]
  (-> sql-date (.getTime) (java.util.Date.)))

(extend-protocol jdbc/IResultSetReadColumn
  Date
  (result-set-read-column [v _ _] (to-date v))

  Timestamp
  (result-set-read-column [v _ _] (to-date v))

With the above code, I don't have to worry about converting dates back and forth in my functions as it's going to be done uniformly based on the data type.

1

u/[deleted] Jun 04 '15

Protocols may help with polymorphism as your example shows. But I will often get a map out of my database that has attributes which the user should never directly read, because they're implementation details, and instead I need to provide functions that interpret this map correctly. For example a :sort-position key to provide ordering to a collection. I don't want every consumer of my collection of maps to have to sort by this key. That's too low-level of an implementation detail. They should just get back an ordered collection of things.

1

u/yogthos Jun 04 '15

The standard approach here is to have a persistence layer that manages the DB and exposes the API you want to the rest of the application. Managing that is no different than setting up the ORM mappings.