software is too hard to compile
this is bad for the ecosystem of software and also culture as a whole
this might sound like a weird claim if you've a) never tried to pull a large software project off a website and build it from scratch, or b) do that all the time. but
it's a problem because it kind of undermines the concept of open source in a pretty basic way. for a lot of software, grabbing the thing and making it do what you want involves an indefinite amount of overcomplicated bullshit as you try to install the right versions of a bunch of dependencies you've never heard of and decipher output from an idiosyncratic build system. you can't just get in there and experiment
which pushes people away from contributing, especially if they have skillsets outside core programmer stuff
i think typically most projects don't see this as an issue, because nobody on the team has a problem with it, and if it gets brought up there are always historical reasons for why it's this way, and it's not THAT complicated, just follow the instructions dumbass,

@aeonofdiscord That was one reason why in the Freenet project we switched to gradle *with the wrapper*: That’s annoying, but it is easy to build as a newcomer if you already run Freenet (because then you already have Java): git clone https://github.com/freenet/fred && cd fred && ./gradlew jar

I wish gradle did not enable that by sidestepping your whole distribution, but by working with it (i.e. on guix it could create a local environment, if docker is available, use that, …), but it works.

GitHub - freenet/fred: Freenet REference Daemon

Freenet REference Daemon. Contribute to freenet/fred development by creating an account on GitHub.

GitHub

@aeonofdiscord That said: GNU autotools fixes that with ./configure && make && make install

but it lacks dependency-support.