I think this is really just anecdotal to your experience. Don’t you need to install a specific version of a compiler or interpreter for every language? Isn’t trying to build any complex project a pray on the first try? I’ve worked in Go codebases where it’s not simply “go build”. It’s: try go build, oops you need to use the make/justfile, oops don’t forget you need to install jq or some other random tool. Complex projects are complex.

▲ Mawr 3 days ago | parent | next [-]

Not at all? There is an obvious difference between modern languages' (Go, Rust, Zig) build systems and the old mess (C++, Java, Python). You have one tool that does everything you need, from formatting and linting to package management and building. No need to choose between Maven or Gradle or try to string together five third party programs that barely work together.

> I’ve worked in Go codebases where it’s not simply “go build”.

A rather funny statement that says the opposite of what you intended. That you can expect most Go projects to be built with just `go build` is high praise.

▲ vips7L 3 days ago | parent [-]

I expect most Java projects to be built with mvn package or gradle build. It doesn’t mean it’s always that simple. Simple projects can be built simply. Complex ones are never handled by 1 tool. There are plenty of examples in Rust and Go where people have to use make or just.

▲ mleo 2 days ago | parent | next [-]

This has been one of my pet peeves on our projects; how simply can I build a project and run it. Ideally with just Java and git, can I download, build and run. Throw in some projects with native libraries, can I build with compiler tools installed but not building 5 other projects first with environment variables pointing to locations of code.

▲ pkolaczk 3 days ago | parent | prev [-]

However, gradle build or mvn install won’t select a proper version of Java to build your code. It won’t even tell you are building with wrong version. Rust, Go, even Scala SBT will.

	▲	ivan_gammel 2 days ago \| parent \| next [-]
		Normally you just define source and compile target and then use whatever JDK supports them. Dependency on exact version is a rare thing. Neither gradle nor Maven are independent native tools, both run on the same JVM they use, so they are not even aware of your specific OS configuration and available JDKs. But they will certainly tell you if your JDK does not support your source or compile target.
	▲	ohdeargodno 2 days ago \| parent \| prev [-]
		> However, gradle build or mvn install won’t select a proper version of Java to build your code. `build.gradle.kts java { toolchain { languageVersion = JavaLanguageVersion.of(17) //bonus: pick your favorite distribution with vendor = JvmVendorSpec.<X> } }` Oh yes they will. > It won’t even tell you are building with wrong version. Right, "Class file has wrong version" doesn't explicitly tell you it's the wrong JDK. Gradle itself runs from a JDK8, so even the install you made with your Windows XP will work fine. If your last experience with Java was 20 years ago and you think that for some reason it hasn't kept up with modern advancement and leapfrogged most languages (how's async doing in rust? virtual threads still stuck nowhere? cool.), sure, keep telling yourself that. You could at least keep it to yourself out of politeness though, or at the very least check that what you're saying is accurate.

▲ bheadmaster 2 days ago | parent | prev [-]

> Isn’t trying to build any complex project a pray on the first try?

I managed to build Docker Daemon - one of the most widely used and complex Go projects - from source with a simple `go build`.

I've never figured out how to build Jenkins from source.

Do you know of any widely used Java project that has a simple build process? Maybe a positive anecdote could change my mind.

	▲	ohdeargodno 2 days ago \| parent [-]
		[dead]