Java 6 dependency in clojure-contrib ok?

[Stuart Halloway]

Perry's proposed props functions (http://groups.google.com/group/clojure/browse_thread/thread/c8ec751b8e66b019/d56ed1200aa95bca
) uses some Java 6 methods.

Is it ok for me to add such things to contrib, or are we maintaining
Java 5 compatibility?

Stu

[Victor Rodriguez]

For what it's worth, I haven't upgraded from Tiger so I'm stuck with
Java 1.5, so I'd like to keep 1.5 compatibility.

Kind regards,

Victor Rodriguez.

> Stu
>
> >
>

[Howard Lewis Ship]

Looks like we need a macro:

(for-jvm 1.5 (....)
1.6 (....))


What's the emoticon for 1/2 sarcastic, 1/2 happy?

--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

[Rich Hickey]

On Apr 8, 7:52 pm, Stuart Halloway <stuart.hallo...@gmail.com> wrote:
> Perry's proposed props functions (http://groups.google.com/group/clojure/browse_thread/thread/c8ec751b8...

> ) uses some Java 6 methods.
>
> Is it ok for me to add such things to contrib, or are we maintaining
> Java 5 compatibility?

I'd prefer we maintain Java 5 for now.

Rich

[Francesco Bellomi]

Looks like an interesting idea for me; it would also allow for
automated dependency analysis for a given target jvm.

btw, I'd also prefer to have 1.5 compatibility

Francesco

[Jeffrey Straszheim]

Yes to 5!  I'm on a Mac and don't feel like dealing w/ upgrading to 6.

[Rayne]

Our God has spoken.

[e]

For what it's worth, I haven't upgraded from Tiger so I'm stuck with
Java 1.5, so I'd like to keep 1.5 compatibility.

 

As an aside, I have Tiger and do stuff with Java 6 all the time.  It's called soylatte:

http://landonf.bikemonkey.org/static/soylatte/

The only thing is that I didn't know my install disk came with X11 for a LONGGGGGG time.  This finally forced me to figure that out so I could install it (my soylatte version, at least, is dependent on having X11 running for some stuff).

[Scott Hickey]

I would strongly recommend Java 5 and plan on staying with that version for a while if you have a goal seeing corporate uptake for Clojure.

The Java version debate comes up every few months on the Groovy lists. The most common argument I've heard was that any company progressive enough to use a language like Groovy or Clojure would be using current versions of Java so there is no harm in using the current version of Java.

My experience consulting for medium and large companies is that this is a false assumption. Most companies are years behind the current Java version but are still open to using new technologies that will run on their current platforms. The web app servers that get deployed usually lag way behind Java releases and converting legacy Java apps to newer versions of Java + app servers is a major project for many companies. They put it off for as long as possible. It may not make sense to those of us trying new languages on the JVM but it is a reality that is out there.

 

Scott Hickey
Senior Consultant
Object Partners, Inc.

---

From: Rich Hickey <richh...@gmail.com>
To: Clojure <clo...@googlegroups.com>
Sent: Wednesday, April 8, 2009 7:31:19 PM
Subject: Re: Java 6 dependency in clojure-contrib ok?

[Chas Emerick]

Agreed.  We'll be supporting Java 1.4 for some time to come still (obviously not using clojure there).  However, we do hope to use clojure for many years to come on Java 1.5 -- I suspect our customers won't be moving off of it for a very long time.

That said, there's lots of stuff in 1.6 and 1.7 that will be extraordinarily useful (which we certainly plan on taking advantage of where we can control the runtime environment), so it seems like we should find a way to support peaceful dependency coexistence.

- Chas