binaries

But WebAssembly binaries are meant to be distributed over the web and instantiated as quickly as possible.

Fuzzing systems find exploits quite effectively in systems that are only available as binaries or APIs.

With Go you can just run a single command to cross-compile binaries that work everywhere.

Usenet was seen as a text-only medium, because binaries were so huge and mostly illegal.

These days much of the functionality of usenet (minus the binaries) is provided by Reddit.

Many years ago I contacted the author and instead of giving me the source he gave me compiled binaries:(.

ISPs that tried to host no-binaries Usenet became the target of PR campaigns.

Every important Usenet server that people used in the US carried binaries.

It even has its equivalent of alt.binaries.pics.* if one is so inclined.

And most importantly, the final binaries you get with Delphi are indistinguishable (size, speed) from those produced by C/C++ compilers, if not better sometimes.

The ISPs I worked at in the late 90s did not carry the binaries groups, becuase of the outrageous storage requirements.

With the growth of binaries groups, the quality of service declined.

Firstly, we would refer to them as proprietary or non-free binaries (perhaps even user-subjugating), not "closed source".

Closed source binaries are profane and immoral (user retains freedom of usage and modification; developer may never "close" the source unless they originated the entire codebase (see: "viral GPL")).