Posted by
ctrueden on
Jul 20, 2015; 8:09pm
URL: http://imagej.273.s1.nabble.com/java-8-and-OSX-tp5013642p5013652.html
Hi Herbie,
> ...you agree that it is ok that software is comparable to green
> bananas and that the user is responsible for debugging.
> Isn't this a bit strange?
To an extent, yes. I wouldn't call it strange, so much as an unfortunate
reality of small development teams.
> Does that mean that you can't run Java 6 under the latest Mac OS? I
> don't think that this holds true.
From Apple's release notes [1]: "OS X El Capitan is the last major release
of OS X that will support the previously deprecated Java 6 runtime and
tools provided by Apple. Applications or features that depend upon Java 6
may not function properly or will not launch when Java 6 is removed.
Developers should move to a newer version of Java as provided by Oracle."
> What's wrong with running Java 6 on an up-to-date personal computer,
> especially if code, such as ImageJ, runs much smoother and faster?
Nothing at all. I would encourage users to use whatever version of Java
best fits their needs. That said, Java 7 fixes many, many bugs that were
never backported to Java 6. Our group's personal experience is that ImageJ
crashes under Java 6 much more often than with Java 7—e.g., when performing
image stitching operations taking many hours.
But if your workflows in ImageJ work well in Java 6, then by all means
stick with it as long as you can.
Regards,
Curtis
[1]
https://developer.apple.com/library/prerelease/mac/releasenotes/General/rn-osx-10.11/On Mon, Jul 20, 2015 at 2:52 PM, Herbie <
[hidden email]> wrote:
> Good day Curtis,
>
> by stating...
>
> [...] Java 8 still has some problems, the only way they will realistically
> be addressed is to do the migration and deal with the fallout."
>
> ...you agree that it is ok that software is comparable to green bananas
> and that the user is responsible for debugging.
> Isn't this a bit strange?
>
> Michael Ellis wrote:
> "Beyond this all I wish to add is a note to anyone involved in ImageJ
> development that moving to newer JVM’s becomes increasingly important as
> the older JVMs become increasingly difficult to get support for on the
> Apple platform [...]"
>
> Does that mean that you can't run Java 6 under the latest Mac OS?
> I don't think that this holds true.
>
> What's wrong with running Java 6 on an up-to-date personal computer,
> especially if code, such as ImageJ, runs much smoother and faster?
>
> Just my 1 Euro Cent questions
>
> Herbie
>
> ::::::::::::::::::::::::::::::::::::::::::::
> Am 20.07.15 um 18:03 schrieb Curtis Rueden:
>
> Hi Michael,
>>
>> Beyond this all I wish to add is a note to anyone involved in ImageJ
>>> development that moving to newer JVM’s becomes increasingly important
>>> as the older JVMs become increasingly difficult to get support for on
>>> the Apple platform and also that anyone doing any development for
>>> plugins is increasingly likely to be tooled up to reply on Java 8.
>>>
>>
>> Indeed, the ImageJ team at LOCI 100% agrees with you, and as announced
>> earlier we do plan to migrate to Java 8 by the end of the summer:
>>
>>
http://imagej.net/2015-06-15_-_Major_updates_in_the_works>>
>> We are definitely feeling the same pain you describe—especially as more
>> and
>> more underlying libraries raise their minimum requirements—and even though
>> Java 8 still has some problems, the only way they will realistically be
>> addressed is to do the migration and deal with the fallout. But of course
>> we being as careful as we can to minimize the chances of backwards
>> incompatible updates.
>>
>> Regards,
>> Curtis
>>
>> On Mon, Jul 20, 2015 at 10:33 AM, Michael Ellis <
[hidden email]>
>> wrote:
>>
>> I too rely on plugins that require Java 8 (lne we build ourselves) and
>>> have also found some problems with ImageJ under Java 8 (slow image
>>> updates
>>> used to be a big problem). These problems seem to have been improving
>>> with
>>> ImageJ releases and also with Java 8 releases.
>>>
>>> I would make sure you have the latests Java 8 installed (some early
>>> versions had show stopping bugs which have since been fixed).
>>>
>>> Beyond this all I wish to add is a note to anyone involved in ImageJ
>>> development that moving to newer JVM’s becomes increasingly important as
>>> the older JVMs become increasingly difficult to get support for on the
>>> Apple platform and also that anyone doing any development for plugins is
>>> increasingly likely to be tooled up to reply on Java 8.
>>>
>>> I understand that desire for backwards compatibility but there’s always
>>> going to be tradeoff!
>>>
>>> — Michael Ellis
>>>
>>> --
>>> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>>>
>>>
>> --
>> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>>
>>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html