Chat Logs

  1. tabmowAnyone taken the plunge and using Zed yet for an editor or ide?
  2. jreicherNo, 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.
  3. whaleyno, 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
  4. dreamrealhttps://bytecode.news/posts/2026/04/cheerpj-4-3-webassembly-based-jvm-for-the-browser
  5. javabotdreamreal's title: "CheerpJ 4.3 - WebAssembly-based JVM for the browser | bytecode.news"
  6. dreamrealanyone here ever use apache fory/fury?
  7. dreamreal(they renamed it)
  8. ParacordWhat's the current sm0rtest way to publish a Java library? I had an account once to sonatype or somesuch but it's long gone.
  9. Paracord...also wtf @ my nick
  10. dreamrealPara: maven central is easy enough, depends on the access
  11. sonOfRaDo 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?
  12. dreamrealI run my own freaking server, so nyar
  13. ParaI'd rather mail my passport to Sudan than deal with PGP :<
  14. ParaGPG. Whatever.
  15. p14nd4i believe PGP (OpenPGP) is the standard, GPG (GNU Privacy Guard) is an implementation
  16. whaleyPara: 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. ParaAh but self-hosting would give me real time stats on the fact that no one wants to use my stuff.
  18. whaleyPara: IIRC, there was some way to just use github packages as a maven repo also
  19. whaleyno idea if that's advisable though... I just remember it existing
  20. ParaGitHub repos are as stable as GitHub itself, which is unfortunately a problem at times.
  21. dreamreal~gpt can I use github to host a maven-generated artifact?
  22. * whaley nods
  23. javabotYes, 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
  24. ParaThat might be what I have to do though, as there's no GPG involved with them.
  25. DoofusCanadensisGitHub Packages can be used per repository or per organization
  26. DoofusCanadensisyou push the artifacts to the repository but can read them from either
  27. DoofusCanadensisif you have any complexity to your artifact repository needs, GitHub recommends their partner, JFrog's Artifactory.
  28. deebojust use artifactory, any time anyone even thinks about it or glances at it, it counts as an api request towards your quota
  29. deebono wait that was nexus
  30. Tenchilol
  31. Tenchitoo true
  32. jbosmansi've used nexus "long ago", and would always do/recommend that for corps, being oldskool as i am i guess
  33. jbosmans"if they can get to your nexus, you've probably got bigger issues"
  34. dreamrealI deployed it locally myself for nevet
  35. dreamrealmanages the java artifacts and the docker images
  36. jbosmansyeah makes sense && good choice imho
  37. dreamrealwas definitely trivial
  38. jbosmansi've never been a big fan of "just use the cloud"
  39. jbosmansunless it's open source ofc
  40. dreamrealI 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)
  41. jbosmansin the end, every app is about I/O :)
  42. jbosmansif ever, i guess i'd (try to) go for open source core, but not everything (every plugin/module/whatever)
  43. dreamrealnevet's licensed under MIT
  44. jbosmansi don't know how that works
  45. dreamrealsimilar to BSD/ASL
  46. jbosmansopenjdk iirc GPLv2
  47. dreamrealbasically open source
  48. dreamrealI refuse to use GPL
  49. jbosmansstronger than open source i think
  50. dreamrealyeah, but viral, and no
  51. jbosmanstypical "more opinions than devs" topic :)
  52. jbosmansi just work for my clients, zero open source :(
  53. Paramy favorite site for looking up licenses https://www.tldrlegal.com/
  54. javabotPara's title: "TLDRLegal - Software Licenses Explained in Plain English"
  55. nevetTLDRLegal - Software Licenses Explained in Plain English
  56. dreamrealyeah, 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.
  57. ParaI generally go either ASF2.0 or MIT (depends slightly on ecosystem) or CC0 if I don't care.
  58. jbosmansyeah enter amazon etc
  59. dreamrealThat's a hard thing to control with *java*, but the intent behind the license is enough to make me want to avoid it.
  60. jbosmanstough nut to crack :)
  61. jbosmansfor me ^
  62. jbosmans(brb)
  63. dreamrealWhat do you mean?
  64. jbosmansoh, i meant (for me) licenses are tough nuts to crack
  65. jbosmansi actually did open source some tooling in my ibm days i remembered, iirc apache 2 license
  66. jbosmansit was around aligning (then websphere) portal theming with frontend dev