Should we remove the downloads provided by the builders?

Points I can immediately think about this:

Reason to remove:
1. These builds are not pegged to any specific release, instead they are just most recent build that has succeeded. Thus are not particularly stable and could lead to unreproducible builds.
2. They have not undergone any QA.
3. No workflow that we actively maintain/care about depends on them.
4. In general they are not considered supported.
5. We don't have the resources/appetite to support them formally.

Reason to keep:
1. Desire to supply users with a simple artifact.
2. Some users, maybe, already have workflows that depend on these binaries.

I am personally of the opinion that this is a situation where a partial solution is worse than no solution. The downloads are not really intended to be production ready nor supported, but a number of recent bugs suggest that users are attempting to integrate them into their workflows as a blackbox solution. This is leaving them in an awkward position when there are issues, since we are unwillingly to fix bugs, but since they are not building it themselves so it is difficult for them to fix it themselves.

An alternative might be to remove various libraries from the downloads, and only ship the user land executables, if those are desired by people. I think if someone is wanting to use the libraries in their project, taking an untested random blob from the internet is the wrong way to do it, building the libraries should be part of their work flow.