chuq%plaid@Sun.COM (Chuq Von Rospach) (10/19/87)
Well, my in-box is inundated, and I think it is time to take some action. There is, without a doubt, an overwhelming demand for comp.sys.mac.hypercard. Can one of the people who send out newgroups that the net will listen to please start this group up? I've got something like 60 yes votes in my list and they're still coming in. As far as my recommendations for other splits, there is interest, and the readers of comp.sys.mac tend to agree that something needs to be done, but in general I don't yet see a consensus of what ought to be done. So rather than go overboard too soon, I'm recommending that the following two groups be created, and we can see how it works out: comp.sys.mac2 comp.sys.mac.programming (rationalization: comp.sys.mac2 is really a different architecture, will run Unix as well as Mac stuff, and as it moves into the market will have a lot of different interests that will make its own set of subgroups necessary. Besides, comp.sys.mac.ii looks funny. Last I looked, abouit 40% of comp.sys.mac was programming oriented. Creating that should help out measurably in comp.sys.mac, even if it doesn't go all the way towards fixing the volume overloads) So it looks like there are three new groups that should be created: comp.sys.mac2 comp.sys.mac.hypercard comp.sys.mac.programming Once comp.sys.mac.hypercard is going, I'll start up the ARPA side of the link. For the time being, I think hypercard stacks should to to the normal Mac source/binary groups, and we'll see where things go from here. thanks for all the feedback! chuq Chuq Von Rospach chuq@sun.COM Editor, OtherRealms Delphi: CHUQ