hirchert@uxe.cso.uiuc.edu (02/26/88)
On the issue of creating a new group comp.binaries.hypercard, is there some reason why it should not be called comp.binaries.mac.hypercard, just as we have comp.sys.mac and comp.sys.mac.hypercard? Comp.binaries.mac.hypercard would be more convenient to me personally and appears to me to be more consistent with the rest of the naming stucture for Mac-related newsgroups. Kurt W. Hirchert National Center for Supercomputing Applications
hirchert@uxe.cso.uiuc.edu (02/27/88)
Bob Webber - Transporting Hypercard stacks in their binary form is a proven technology that is reasonably efficient in its use of network bandwidth. So far, none of us has seen a complete "source" transport system for Hypercard. You seem to think that it would be easy to do. The rest of us remain unconvinced. If you can demonstrate an easy and reliable way of reducing stacks into "source" components and then reconstructing them back into a stack, I would be happy to consider distributing stacks in "source" form. Until such a technology is proven workable, we need to stick to distributing stacks with the proven technology. Kurt W. Hirchert National Center for Supercomputing Applications