Prev: Centralizing instantiation?
Next: Display Byte value for GB2123 Character
From: ClassCastException on 25 May 2010 18:57
Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
Half-Life 3 -- that is to say, vaporware?

Because I swear it's been like *years* since I first heard mention of it
and JDK 6 still seems to be current.
From: Jeff Higgins on 25 May 2010 19:03
On 5/25/2010 6:57 PM, ClassCastException wrote:
> Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
> Half-Life 3 -- that is to say, vaporware?
>
> Because I swear it's been like *years* since I first heard mention of it
> and JDK 6 still seems to be current.
<http://openjdk.java.net/projects/jdk7/>

From: Arne Vajhøj on 25 May 2010 19:36
On 25-05-2010 18:57, ClassCastException wrote:
> Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
> Half-Life 3 -- that is to say, vaporware?
>
> Because I swear it's been like *years* since I first heard mention of it
> and JDK 6 still seems to be current.

It has been a long time underway.

But people are working on it.

And eventually it will come out.

Lot of people are unhappy with the speed, but ...

Anyway - Java is so mature so there are very few must haves
missing and for each nice to have there are 7 different
opinions on how to implement.

Arne

From: ClassCastException on 26 May 2010 00:50
On Tue, 25 May 2010 19:36:47 -0400, Arne Vajhøj wrote:

> On 25-05-2010 18:57, ClassCastException wrote:
>> Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
>> Half-Life 3 -- that is to say, vaporware?
>>
>> Because I swear it's been like *years* since I first heard mention of
>> it and JDK 6 still seems to be current.
>
> It has been a long time underway.
>
> But people are working on it.
>
> And eventually it will come out.
>
> Lot of people are unhappy with the speed, but ...
>
> Anyway - Java is so mature so there are very few must haves missing and
> for each nice to have there are 7 different opinions on how to
> implement.

Oh, lovely, so it will be another six months to six years in coming and,
when (if) it finally does show up, it will have "designed by committee"
written all over it?

Maybe it's best to just stick with JDK 6 then. :)
From: Arved Sandstrom on 26 May 2010 05:35
ClassCastException wrote:
> On Tue, 25 May 2010 19:36:47 -0400, Arne Vajhøj wrote:
>
>> On 25-05-2010 18:57, ClassCastException wrote:
>>> Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
>>> Half-Life 3 -- that is to say, vaporware?
>>>
>>> Because I swear it's been like *years* since I first heard mention of
>>> it and JDK 6 still seems to be current.
>> It has been a long time underway.
>>
>> But people are working on it.
>>
>> And eventually it will come out.
>>
>> Lot of people are unhappy with the speed, but ...
>>
>> Anyway - Java is so mature so there are very few must haves missing and
>> for each nice to have there are 7 different opinions on how to
>> implement.
>
> Oh, lovely, so it will be another six months to six years in coming and,
> when (if) it finally does show up, it will have "designed by committee"
> written all over it?
>
> Maybe it's best to just stick with JDK 6 then. :)

Even better, continue working with JDK 6, and if you're a
dyed-in-the-wool JVM person, expand your programming horizons with Scala
or Clojure. For example, if you're working with J2EE on Weblogic, but
see a problem that is really better addressed using functional code,
write that portion using Scala, for example.

AHS
 |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: Centralizing instantiation?
Next: Display Byte value for GB2123 Character