!aRKdLCkUeIFjRPZuJT:nixos.org

NixOS JVM

129 Members
28 Servers

Load older messages


SenderMessageTime
24 Sep 2024
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️I thought it was built from source but I could just be misremembering19:23:38
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Okay yeah no it was just substituted in where the source JDKs get built which is where I got it wrong19:26:11
@emilazy:matrix.orgemilyright. so it's unclear to me why we need both Zulu and Temurin, they seem quite redundant19:27:06
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Not sure, I don't use Darwin so I just didn't touch that part lol19:28:19
@emilazy:matrix.orgemily(and Corretto also seems sufficiently niche that I question whether it's worth maintaining in-tree)19:28:26
@emilazy:matrix.orgemilymy fear about shipping 8 indefinitely, when Debian and Ubuntu have already given up on it, is that it has 6 years of life left. newer versions will continue to diverge from it, requiring more build conditionals and complexity, and it may become increasingly painful to keep building with the modern compilers and libraries in Nixpkgs19:29:16
@emilazy:matrix.orgemilyfor instance, I've had to manually backport FFmpeg support patches to older versions of OpenJFX, which is quite a maintenance drag19:29:34
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️That's the kind of situation where we keep JDK 8 but stop supporting it for stuff like that19:29:56
@emilazy:matrix.orgemily(not directly OpenJDK admittedly, but it gives an example of the churn caused by packaging many old versions of things)19:29:56
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️JDK 8 itself is still important just because so, so much still relies on it But we don't necessarily need to actively back port stuff if it isn't necessary for other packages19:30:32
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Java 8 truly is the version that will not die19:31:02
@emilazy:matrix.orgemilywell, if I hadn't spent the effort to backport FFmpeg support there then we would be keeping old FFmpegs in the tree even longer, which would be a drag on FFmpeg maintenance. carrying ancient software tends to act as a drag on the rest of the ecosystem in that way, where carrying one thing causes indefinite amounts of additional maintenance effort on other people throughout the tree. but fair enough, I get that Java 8 is particularly widely used and likely deserves some special status there (although I wonder what Debian/Ubuntu users are doing?) – but 11 and 17 aren't nearly so ubiquitous, right?19:32:18
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Yeah19:32:54
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️ rging in Nixpkgs, there is actually less usage than I expected, though it's hard to tell what usage is like out-of-tree 19:33:50
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️ (Part of me wants to lib.warn "Hi! Please respond to this poll if you are still using JDK 8") 19:34:11
@emilazy:matrix.orgemilythat would break CI unless you removed all the in-tree users sadly :)19:36:21
@emilazy:matrix.orgemilyyou have to do some hacks to warn on a package without breaking the channels19:36:27
@emilazy:matrix.orgemilyanyway, sorry to come in here like "hi, I don't know anything, can we get rid of all this stuff" 😅 it's just quite painful to remove or package a new JDK right now, and it really doesn't seem like we should need more than ~3 distributions19:37:29
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️No worries! We definitely have room to trim down, like with Zulu as mentioned, that could definitely be replaced with Temurin if I'm reading things correctly.19:38:21
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️I don't think we should simply remove for the sake of removing, where possible, but when it's actively a maintenance burden it's worth it.19:38:55
@emilazy:matrix.orgemilysadly every package causes some kind of burden – if only by slowing down Hydra evaluation and build times and causing the channels to bump slower for everyone. but in this case it's a security burden too, since 22 is now EOL and someone has to go in and deal with every single copy of it and bump to 2319:40:32
@emilazy:matrix.orgemilyit seems like the main difference between Zulu and Temurin is that the former bundles OpenJFX. I don't know if it's possible for us to use our source OpenJFX build with Temurin or not?19:40:55
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Hmm, that would be a problem19:41:30
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️OpenJFX is bundled in at compile time iirc19:41:38
@emilazy:matrix.orgemilyah, so we ship Zulu for macOS because it's the only option to get JavaFX there, I suppose19:43:33
@emilazy:matrix.orgemilyI was told that nobody actually really cares much about JavaFX recently :) but maybe it would make more sense to standardize on Zulu instead of Temurin, then?19:43:56
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️ Temurin is pretty much the standard binary release of OpenJDK, so I don't think we'll switch over 19:47:10
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️(It's descended from the original AdoptOpenJDK, for reference)19:47:23
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Plus not everything needs OpenJFX19:47:34
@infinidoge:inx.moeInfinidoge 🏳️‍⚧️Ideally, we'd do a source build of JDK and JFX for Darwin, but that takes effort lol19:47:55

Show newer messages


Back to Room ListRoom Version: 6