It's not only a matter of what's supported but also what is generally
deployed. I believe Java 5 is still widely used out there. Macs for
example ship with it by default and (I believe) Java 6 for Mac OS X is
still in beta. Making sure that we are still compatible with Java 5
gives these people the possibility to use SC and this is what matters most.
We could also tell them to update, have the installer trigger an
optional update or bundle Java 6 with SC package (ugly). If we really
wanted to, we could always find solutions.
I had your private message where you said that Sun would stop supporting
it after October 2009. If it turns out to be true then I guess we could
probably start thinking about removing the J5 compatibility constraint
as soon as next October.
Anyway, this possible end of support would be for post 1.0, of course.
Note that the fact that Sun would stop releasing J5 updates does not
mean that people would stop using it and automatically switch to J6.
Quite often users are not even aware that they have java running on
there computer, so we shouldn't count on a lot of reactivity.
IMHO we shouldn't encourage people to usea broken (yes, unmaintained is
broken) Java. It's a vicious circle: I don't update my Java because my
software won't demand it, the sofware don't require a new version of
Java because a part of the user base still uses the old version.
Well, in addition to the above I don't really see any compelling reason
not to. The difference between J5 and J6 is not as big as it was between
4 and 5 so it's easy to use J6's advantages without breaking backward
compatibility. The jdic problems were, I believe, the first that were
caused by it and that was mostly because of the weird systray support in
J6 rather than anything in J5.
If the code in SC doesn't diverge depending of the version of the JRE,
this "free" backward compatibility is no problem. Otherwise, it'll
double the platforms to test and make the work for the maintainer of
that code harder.
That said, I don't even know the amount of changes needed to switch
between JDIC and the Java 6 API, and I never wrote a single line of code
for that part of SC, so I can't tell if it's really a problem in this
very case. I just used the occasion to discuss this topic.
Does this answer your question?
Yes, thanks for this comprehensive answer.
On Sat, Dec 13, 2008 at 12:41:05AM +0200, Emil Ivov wrote:
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org