Subject: Re: some observations on the peripheral market
To: David A. Gatwood <>
From: John Nemeth <>
List: port-macppc
Date: 01/10/1999 17:21:08
On Jan 10,  6:52pm, "David A. Gatwood" wrote:
} On Sun, 10 Jan 1999, wb2oyc wrote:
} > And then there's this one; the 'S' is USB isn't for Serial, its for 
} > SLOW!  Just wait till you put everything on it, and one device kills
} > the buss....and NOTHING WORKS!  It isn't even off the ground yet and

     Somebody else made the comment that USB is designed to protect
against this.  I'd just like to say it is impossible to prevent a
device from doing something it shouldn't and killing the bus,
including doing physical damage to other devices on the bus, since
they can do things like continuously pummel the bus with data, ground
out signal lines, etc.  However, this risk is shared by every bus
inexistance.  I would say that the benefits outweigh this risk, which
in reality is very small.

} > already there's FireWire.  Its just another way for them to get you 
} > to spend money to throw away what you already have, thats probably 
} I have to defend FireWire (a.k.a. Sony iLink, a.k.a. IEEE-1394, I think). 
} It's been an industry standard in digital video production for some time
} now.  I've been doing video editing with Radius's FW card since late
} summer or so, and the hardware's been out for quite a lot longer than
} that.  I've never seen it do anything besides video, but it seems to be a
} solid bus, or at least I haven't had any real trouble with it.  Even

     It's easy to be solid when only doing one thing.  It's a lot
harder when there are multiple devices involved, which may or may not
obey the bus specifications.

} However, I do agree that Apple should maintain ADB support in their future
} machines, if for no other reason, then because I don't want to have to
} port NetBSD's usb support to MkLinux.  ;-)

    Why not just use NetBSD/macppc?  Does MkLinux support FireWire?

}-- End of excerpt from "David A. Gatwood"