[news.eclipse.technology.ohf] Re: Java 1.4 vs 1.5

[Grahame Grieve <grahameg@xxxxxxxxxxxxxxx>]

Well, I've just spent a few hours playing with V3 messages.
It's just too hard to do without generics. Possible, probably,
but you spend increasing amounts of time trying to make up
for not having the same inheritence patterns

So 1.5 it will be

Grahame

Jesse Kuhnert wrote:
> I'd say that would be true, if you were planning on going to production 
> with this code in about a month or two, but something tells me that's 
> not really a requirement of this project.
>
> The trends in a lot of the other open source projects (hibernate, 
> eclipse, tapestry, etc..etc..) seem to be everyone either currently 
> supporting or actively supporting varying levels of 1.5.
>
> The last and final sort of measurement for jdk stability might be the 
> number of bug postings found, with the greater the number being a good 
> thing generally(i think)...1.4 has about 5000 or so and 1.5 has about 
> 3000..Sounds like it'll be plenty stable by the time anyone goes into 
> production with this.
>
> (P.S. And annotations too I hope? It would be nice to eliminate more and 
> more xml/configuration files, not that you have any defined yet, but in 
> case you do. heh)
>
> I think the only thing anyone could ever potentially question going to 
> production with for server stuff would be windows. ;)
>
> jesse
>
> Grahame Grieve wrote:
>
> > An interesting question arose and I'd like to hear
> > from anyone with an opinion. I'd like to use generics,
> > but this requires v1.5, and it has been put to me that
> > it's still to early to write code using v1.5 that is
> > intended for server production deployment.