3 ms·
> there's no reason not to be using Java 8. I wish. When life (or rather a vendor) gives you java 6 libs which barely work on java 7, you make java7 lemonade.
by toyg 10y ago
> there's no reason not to be using Java 8.
I wish. When life (or rather a vendor) gives you java 6 libs which barely work on java 7, you make java7 lemonade.
- koolba 10y agoWhat kind of crappy library doesn't work on a newer version of Java? The only thing I can see breaking would be reflection based invocations of new methods on existing interfaces (ex: Foo has a .bar() in Java 7 but not Java 6). You'd have to be doing something pretty unusual for that to bite you.
- toyg 10y ago> What kind of crappy library doesn't work on a newer version of Java? Oracle middleware libraries (to be fair, mostly acquired)... I believe the problem was that in Java 8, something related to StringBuilder or string parsing was breaking hard. With Java7 it was ok, so we went with that.
- koolba 10y agoAh that's not a compatibility issues so much as a change in performance. I think they changed the defaults for String interning. In the vast majority of cases it's be a performance improvement but if you were manually managing lots of small Strings (ex: custom file processor reading misc user input) then it could get out of control.