Live data from Hacker News

Don't use Java 7 for anything, unless you have no loops in your program

lucidimagination.com

21–29 of 29 posts

Re: Don't use Java 7 for anything, unless you have no loops in your program

#25
Smells a bit like FUD to me. We've been using openjdk 7 in production for quite a while now with no problems. This is on million+ LOC applications using various open source software (however, not Lucene or Solr :-)).

I suggest if you're worried, test it and see what happens. This bug sounds like it will hit you immediately if there is a problem.

Re: Don't use Java 7 for anything, unless you have no loops in your program

#26

This blog format is absurd. Narrow column and a fixed width content in a box guaranteed to be smaller than the content. Plus this is effectively blog spam despite being owned by the same place as the original content: http://www.lucidimagination.com/search/document/1a0d3986e48a...

Here's the original source for Uwe's email: http://mail-archives.apache.org/mod_mbox/www-announce/201107...

Not sure why a third level reference is being passed around.

Re: Don't use Java 7 for anything, unless you have no loops in your program

#27
post #26

This blog format is absurd. Narrow column and a fixed width content in a box guaranteed to be smaller than the content. Plus this is effectively blog spam despite being owned by the same place as the original content: http://www.lucidimagination.com/search/document/1a0d3986e48a...

Here's the original source for Uwe's email: http://mail-archives.apache.org/mod_mbox/www-announce/201107... Not sure why a third level reference is being passed around.

Oh great, so I was still using some gated linked. Thanks for the original, it's even easier on the eyes than my source anyway.

Re: Don't use Java 7 for anything, unless you have no loops in your program

#28

More generally, don't use anything on the day of release... Wait a week or 2 for the bugs to be ironed out. Surely we've all learnt that by now...

Certainly with Java (speaking from experience going back to 1.0) and most certainly with major language/compiler releases like this one (see 1.5 previously). Java almost always requires a dot-release or two after a major version to iron out the kinks. Which isn't to say don't try it, but try it in development with low expectations. On the other hand, they're usually very quick about turning out the next few dot-releases (I'd wager that it'll be 1.7.3 by September, unless they continue with the silly 1.6.0_xx version format in which case 1.7.0_03).
Post reply on HN