For what it's worth, there's been a similar discussion about Scala
and Java 5 over on the Scala mailing list.
The key reason for keeping Scala @ 1.4 is that there is no Open
version of Java 5+ Yes, Sun has open sourced 95% of the JDK, but the
other 5% bars folks from actually releasing an Open version of the
JDK. On the other hand, the Open JDK clones are @ 1.4 and the Scala
team wants to be able to distribute Scala with an Open JDK.
On a private list, some folks took an informal survey of JDK 1.4 vs.
Java 5 usage. It turns out that no one from a public company was
able to guarantee that Java 5 was available on all their production
servers. Most of the companies were migrating to Java 5. Kaiser
(the CA HMO) as of 9 months ago had just completed its JDK 1.3 to JDK
1.4 migration (they are at one end of the "conservative" spectrum.)
Personally, I like all the library and annotation features in Java 5
and think that folks who don't move there are sloths. But I tend to
live on something that looks like a bleeding edge.
My 2 cents.
On Jul 24, 2007, at 1:27 AM, dreamhead wrote:
+1
2007/7/24, Charles Oliver Nutter <[EMAIL PROTECTED]>:
- Annotations for specifying method bindings. This could largely
eliminate the need for manual method-binding code, as well as
allow us
to split method implementations by arity and even argument type
I really like this idea.
As we know, we can port most Java 5 features back to 1.4 in bytecode
level except annotation. But I think it's OK if annotation is just
used for code generation.
--
Everything is simple!
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
David Pollak
http://blog.lostlake.org
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
