Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!bu.edu!purdue!iuvax!rutgers!aramis.rutgers.edu!paul.rutgers.edu!jac From: jac@paul.rutgers.edu (Jonathan A. Chandross) Newsgroups: comp.sys.apple2 Subject: Vote YES on comp.sources.apple2 Message-ID: Date: 17 Jul 90 18:31:35 GMT References: <5669071@ub.cc.umich.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 67 I would be much happier if Bakal could have restricted himself to posting his opinions during the discussion period when they were appropriate. Waiting for the call for votes is really in poor taste. Tabakal@UB.CC.UMICH.EDU > As someone involved in the distribution > of apple ][ pd/shareware, it's enough to have to deal with the > sources we have now (mainly apple for notes, nosc for beta kermits, > comp.binaries.apple2, apple2-L, as well as visiting the various > other FTP sites to see what we've missed earlier). Say what? You got *too* much software so you want to cut down on anything that will produce *more*? How do you answer all the people who complain that developers won't write for the Apple // -- "That's ok, we have too much software already." Nobody *forces* you to read/use sources. Ignore them if you want, but don't restrict others who *want* this information. > I personally do not get comp.sources.* and would probably miss > a good deal of stuff if it came in. Ahhhh, the truth comes out. You don't get the group so you don't want anyone else to. Did you ever consider that you can update your feed to get only the groups you want? You don't have to take the whole hierarchy, you know. If you get comp.sys.apple2 and comp.binaries.apple2 I suspect you wouldn't have any trouble adding comp.sources.apple2. Why not ask you sysadmin before you complain that "my site doesn't get the sources groups so I don't want a new group." > Generally, sources are *larger* than executables, so I do not > think that removing them from the binaries will make them > more accessible. Say what? Sources are generally smaller, since they don't have libraries, are at a much higher level, etc. than a binary. The issue is not removing them from the binaries because of their size, but because SOURCES ARE NOT BINARIES. SOURCES ARE NOT OBJECT CODE. That's why they don't belong in a binaries group. Findally, if the binaries groups are such a great place for sources, why don't we see more sources there? Because they don't belong. Pure and simple. The current setup does not encourage distribution of Apple // sources. If it did we would see them. > If anything, it may lead system administrators > to remove comp.sources.apple2 from sites, thus restricting rather > than expanding their distribution. Are you kidding? If volume was a problem, comp.sys.apple2 would have been deleted long ago. What do you base this assumption on, anyway. > Providing more and better resources is a excellent goal for the > online "net" community, but I fear that comp.sources.apple2 will > merely detract from substance in order to better fit the usenet > naming protocol. What is the point of this? The substance is SOURCE to Apple // programs. That surely fits in with the newsgroup guidlines. Jonathan A. Chandross Internet: jac@paul.rutgers.edu UUCP: rutgers!paul.rutgers.edu!jac