Back to the channels

#java

00:51 tabmow Anyone taken the plunge and using Zed yet for an editor or ide?
00:55 jreicher No, but I haven't tried any AI yet. I'd be interested to know how it compares with mature languages servers though. I've been very happy with LSP so far.
00:58 whaley no, because 1) the name reminds me of Zed Shaw 2) all of this bullshit is just the peak of inflated expectations in another dumb fucking hype cycle and 3) Zed's dead, baby... Zed's dead
11:25 dreamreal https://bytecode.news/posts/2026/04/cheerpj-4-3-webassembly-based-jvm-for-the-browser
11:25 javabot dreamreal's title: "CheerpJ 4.3 - WebAssembly-based JVM for the browser | bytecode.news"
13:05 dreamreal anyone here ever use apache fory/fury?
13:05 dreamreal (they renamed it)
16:54 Paracord What's the current sm0rtest way to publish a Java library? I had an account once to sonatype or somesuch but it's long gone.
16:54 Paracord ...also wtf @ my nick
16:56 dreamreal Para: maven central is easy enough, depends on the access
16:57 sonOfRa Do they still do that silly dance where you have to GPG sign every release, but don't actually have to put the public key anywhere, so they can't verify who signed it, but hey it's signed so it's secure?
16:58 dreamreal I run my own freaking server, so nyar
16:59 Para I'd rather mail my passport to Sudan than deal with PGP :<
17:00 Para GPG. Whatever.
17:03 p14nd4 i believe PGP (OpenPGP) is the standard, GPG (GNU Privacy Guard) is an implementation
17:55 whaley Para: I'm not up to speed, but last time I checked, any publicly hosted and maintained maven repo woudl do. You could even self host. Just make sure your libary's instructions mention needing to reference that repo, or at least mirror it. Though sonatype's is included by default and there's a good chance it's not going anywwhere anytime soon (unlike anything self hosted).
17:56 Para Ah but self-hosting would give me real time stats on the fact that no one wants to use my stuff.
17:56 whaley Para: IIRC, there was some way to just use github packages as a maven repo also
17:56 whaley no idea if that's advisable though... I just remember it existing
17:57 Para GitHub repos are as stable as GitHub itself, which is unfortunately a problem at times.
17:57 dreamreal ~gpt can I use github to host a maven-generated artifact?
17:57 * whaley nods
17:57 javabot Yes, you can use GitHub to host a Maven-generated artifact. Maven artifacts can be pushed to a GitHub repository and then accessed as a dependency in your project. You can use GitHub Packages, which is a package hosting service integrated with GitHub. To get started, refer to the official GitHub documentation: https://docs.github.com/en/packages/guides/configuring-apache-maven-for-use-with-github-packages
17:58 Para That might be what I have to do though, as there's no GPG involved with them.
18:00 DoofusCanadensis GitHub Packages can be used per repository or per organization
18:00 DoofusCanadensis you push the artifacts to the repository but can read them from either
18:02 DoofusCanadensis if you have any complexity to your artifact repository needs, GitHub recommends their partner, JFrog's Artifactory.
18:22 deebo just use artifactory, any time anyone even thinks about it or glances at it, it counts as an api request towards your quota
18:23 deebo no wait that was nexus
18:23 Tenchi lol
18:23 Tenchi too true
19:10 jbosmans i've used nexus "long ago", and would always do/recommend that for corps, being oldskool as i am i guess
19:10 jbosmans "if they can get to your nexus, you've probably got bigger issues"
19:10 dreamreal I deployed it locally myself for nevet
19:11 dreamreal manages the java artifacts and the docker images
19:11 jbosmans yeah makes sense && good choice imho
19:11 dreamreal was definitely trivial
19:11 jbosmans i've never been a big fan of "just use the cloud"
19:11 jbosmans unless it's open source ofc
19:12 dreamreal I don't know why anyone else would really want nevet's core unless they were building a similar ingress/egress app (which ... actually should be pretty common, nevet's core is surprisingly general-cased)
19:12 jbosmans in the end, every app is about I/O :)
19:13 jbosmans if ever, i guess i'd (try to) go for open source core, but not everything (every plugin/module/whatever)
19:14 dreamreal nevet's licensed under MIT
19:15 jbosmans i don't know how that works
19:15 dreamreal similar to BSD/ASL
19:15 jbosmans openjdk iirc GPLv2
19:15 dreamreal basically open source
19:15 dreamreal I refuse to use GPL
19:15 jbosmans stronger than open source i think
19:15 dreamreal yeah, but viral, and no
19:16 jbosmans typical "more opinions than devs" topic :)
19:16 jbosmans i just work for my clients, zero open source :(
19:16 Para my favorite site for looking up licenses https://www.tldrlegal.com/
19:16 javabot Para's title: "TLDRLegal - Software Licenses Explained in Plain English"
19:16 nevet TLDRLegal - Software Licenses Explained in Plain English
19:16 dreamreal yeah, but that's a choice I find pretty easy to make: when I make it so that anything that USES my code might be licensed under my license? ew.
19:17 Para I generally go either ASF2.0 or MIT (depends slightly on ecosystem) or CC0 if I don't care.
19:17 jbosmans yeah enter amazon etc
19:17 dreamreal That's a hard thing to control with *java*, but the intent behind the license is enough to make me want to avoid it.
19:18 jbosmans tough nut to crack :)
19:18 jbosmans for me ^
19:18 jbosmans (brb)
19:18 dreamreal What do you mean?
19:54 jbosmans oh, i meant (for me) licenses are tough nuts to crack
19:56 jbosmans i actually did open source some tooling in my ibm days i remembered, iirc apache 2 license
19:56 jbosmans it was around aligning (then websphere) portal theming with frontend dev