Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 SMI; site sun.uucp Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!zehntel!dual!amd!decwrl!sun!gnu From: gnu@sun.uucp (John Gilmore) Newsgroups: net.sources,net.news Subject: Posting object code to net.sources Message-ID: <1604@sun.uucp> Date: Wed, 8-Aug-84 06:53:40 EDT Article-I.D.: sun.1604 Posted: Wed Aug 8 06:53:40 1984 Date-Received: Fri, 10-Aug-84 02:35:54 EDT References: <1094@sdcsvax.UUCP> Organization: Sun Microsystems, Inc. Lines: 16 Recently there's been a rash of uuencoded object code in net.sources. I think this is a despicable practice, because source is not provided. One of the great things about this network is that there's a large (LARGE) variety of machines on it. Something posted in object is useful on exactly one class of machines. Furthermore, recipients can't fix bugs or make enhancements -- let alone consider porting the software to a different environment. While free object code w/o source is sometimes better than no code at all, I don't think net.sources is the right place for it. I think that posting object code without source should be discouraged, in Emily Post and by replies to people who do it. Is this the "sense of the net" or am I off in a corner? Followups to net.news only, please.