This is one of my old projects that I brought into my company several years ago and have been sitting on for a while. If any of you remember LimeWire, this is forked from their last release before they went under, to which we’ve added better search, a new torrent engine from FrostWire, and our own eDonkey code - plus a huge facelift in Compose (i.e. Kotlin) rather than Java Swing, which has undeniably grown a bit crusty and unresponsive/slow.
To peel back the veil a little, I was the manager on the old project, rather than a coder, but the effort kind of petered out over the 6.1 release, back when I was still in high school/early uni (if I say “first Trump administration”, that should give you an idea). I thought this was a waste, and now with my own business etc., I thought it would be nice to revive it.
It’s managed Java code (“managed” meaning, runs on a VM like Elixir or Erlang—I’m mostly an Elixir/Lisp/Haskell guy who taught himself imperative programming out of necessity), so it should be fine on any system (with the possible exception of the torrent code, but I think I fixed that). Building is by Gradle (formerly Apache Ant). The only thing I did to it personally, mind, is the Kotlin facelift, everything else was either FrostWire or done by one of my colleagues. Not that the Kotlin facelift was easy…
Unfortunately, I haven’t yet successfully popped my pull-request cherry and trying to get this carried by HaikuPorts has been a capital-E Effort, and I’d like to take a moment to ask for help.
I haven’t actually used AI for this, never mind that someone commented:
The whole “Linux rollout orchestrator” stuff over that repo reeks of LLM usage (lots of “plans” and .md files for “agents” to process).
I vote to close this as-is. Why give it any thought/effort/time, when there’s no proper author in the loop?
If not “AI”, more effort is expected anyway.
What I did was hack together an Elixir script that would attempt to publish this to multiple Linux distributions as well as Haiku, because trying to release to 10-12 repos by hand just seems like far too much faff for a Java project, as in “write once, run anywhere”…