3 ms·

I definitely agree about URL's in go. Maven comes up all the time as an example of packaging done correctly. It just does JVM stuff though, right? Seems like

I definitely agree about URL's in go. Maven comes up all the time as an example of packaging done correctly. It just does JVM stuff though, right? Seems like it's winning at an easier game. Reproducible builds are a hard thing to achieve in the general case. Even something as simple as packaging your files in a tar will blow your determinism. I think retooling for determinism is worth spending time on, but I'm not sure I could convince my boss of that. So far as I'm aware, all dependency systems are bad. Nix is the least bad one I know.

jmyeet 3y ago
So Java is for JVM languages and binaries. That includes things people probably don't care about anymore (eg Groovy, Clojure, Kotlin, Scala) because they all compile to JVM bytecode so as far as Maven is concerned, they're indistiYou cannguishable. You can include any static assets you want (eg css, js, html files). I honestly haven't looked into that. Putting static assets in a project is relatively straightforward but a JS depdendency? Yeah, that's probably a no go. Or it's really awkward. For hermetic builds, given a blank slate, I'd probably start with Bazel.