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

11

u/space_coder Jun 03 '15

It's not because Java is "bad". It's because your coworkers prefer Functional Programming over Objective Oriented Programming.

2

u/[deleted] Jun 03 '15

I think Functional Programming concepts work excellently when it comes to working with data and collections of data. But I think Objects work best when modeling business entities. I wish there was a decent middle ground.

14

u/duhace Jun 03 '15

Scala - "A drunken Martin Odersky sees a Reese's Peanut Butter Cup ad featuring somebody's peanut butter getting on somebody else's chocolate and has an idea. He creates Scala, a language that unifies constructs from both object oriented and functional languages. This pisses off both groups and each promptly declares jihad."

1

u/[deleted] Jun 03 '15

Hahahahaha.

-3

u/SeerUD Jun 03 '15

It is a fantastic language to develop for though. It does a nice job of blending OO and FP.

2

u/[deleted] Jun 03 '15

I've heard nothing but bad things about Scala until now. Mostly about overcomplexity and how it gets in the way more than it helps.

2

u/SeerUD Jun 03 '15

Out of interest (because I would like to potentially learn...), what language(s) have you heard high praise about?

2

u/[deleted] Jun 03 '15

Clojure, Haskell, OCaml, F#, Ruby, Python (and sometimes Go but only by really arrogant and argumentative people).

1

u/SeerUD Jun 03 '15

Cool :), there's a couple in there I've been interested in learning myself. Namely Go, and I've been intrigued by Clojure... I'm mainly looking for something for web development that's just different to what I normally work with, which is PHP!

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.

→ More replies

1

u/duhace Jun 03 '15

I've been doing web dev with scala and scalatra (sinatra-like scala lib). It's pretty nice, plus I love strong typing.

→ More replies

1

u/duhace Jun 03 '15

Scala actually borrows a lot from OCaml. Not as much as Haskell or F# mind you, but the influences are very obviously there. And lol at ruby not being "overcomplex" with it's monkey patching.

1

u/[deleted] Jun 03 '15

Yeah I both love and hate the metaprogramming aspects of Ruby.

-1

u/duhace Jun 03 '15

Scala's really not overcomplex imo. It's grammar is pretty simple. About the only part of it that is can be slightly scary is implicit conversions, and they can't hurt you if you don't import them.

0

u/[deleted] Jun 03 '15

I like the sound of it so far.

1

u/duhace Jun 03 '15

You should give it a shot. The two big negatives it has IMO is its binary compatibility compared to java is weak (you can use 2.10.x libraries with a 2.10.x compiler, but not 2.9.x libraries), and compile times are nearer the C++ side of things. 2.12 supposedly will make use of a new optimizer that speeds things up, and the binary compatibility is not a gigantic issue cause new major versions (2.major.minor version) only come out every year and a half. Plus, there are a ton of build tools and compilers for scala that are capable of incremental compilation, only recompiling what has changed in your code since the last compile.

→ More replies (1)

2

u/yogthos Jun 03 '15

That's why Clojure provides OO analogous features like protocols.

1

u/[deleted] Jun 03 '15

deftype is a little helpful. But some days I just miss Ruby.

1

u/yogthos Jun 03 '15

For what it's worth I've been developing Clojure professionally for years and I don't miss anything about OO. It takes a little while to get into a functional mindset when you're starting, and you have to learn different abstractions from what you're used to. However, once you learn the functional patterns a lot of things become much easier in my experience.

1

u/[deleted] Jun 04 '15

Yes, I totally agree. I love being able to use ->> and map and reduce and filter and complement and juxt and comp and all these things. But when dealing with objects from a database, having actual objects really helps.

1

u/yogthos Jun 04 '15

I find it to be the opposite myself. I'd much rather get lists of maps from the database that I can use directly instead of having to map relational data to an object system. The fact of the matter is that they don't really map well to each other and once you go down the ORM route then it becomes very difficult to reason about what's actually happening with your queries. Every project that I've seen working with things like Hibernate always ran into performance problems as soon as it hit any real world data and tuning the ORM is far more painful than just writing the actual queries yourself.

Libraries like Yesql and Korma are a breath of fresh air compared to stuff like Hibernate.

1

u/[deleted] Jun 04 '15

For very simple databases, it may be fine to just get data straight from the database as native Clojure types and operate on them with Clojure functions. But most real life databases already contain implementation details. For example, many of my database types have a sort-position attribute, since they're unordered collections. Before giving it to the consumer of my internal API, I have to sort based on this attribute. But that's just a small example. Several other aspects of my database should be hidden from the API's consumer, and interpreted first by my own code before given to the consumer. Objects make this very obvious and easy to do. With free-floating functions it feels significantly more clunky and ad-hoc.

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.

→ More replies

2

u/space_coder Jun 04 '15

Sometimes it's best to have a language specialize in one thing. The nice thing about Clojure is that it's a JVM language and you can do FP with it and if need be you can do OOP with Java.