8 comments

[ 4.2 ms ] story [ 32.5 ms ] thread
ADB was pretty solid. A shared-single-wire bus that allows multiple slaves by including an address in the message... but includes a protocol-level reset that's used regularly, so a missed single bit doesn't jam things up unrecoverably. When I think of how many fewer hours of my life I would have wasted had I2C learned this lesson...
The only thing was… it was very easy to destroy a device (keyboard for example) if you hot-plugged it. I lost a keyboard or two (well, my employer did) because I plugged in a device without first powering down the Mac. (Unlikely the ADB protocol though? I wonder if this is one of those examples where having some pins longer than others so they get electrical contact first could have prevented the problem.)
As the author mentions doing it, a note regarding retrobright: it seems to cause faster yellowing than not using it. https://youtu.be/_n_WpjseCXA

Maybe just let your items show their age.

Honestly it'd be really cool to see some repro parts for these like an upper case (even without the Apple logo).

I junked my old AE2 ages ago and finally got a replacement today. If I knew then what I know now I would've salvaged a bunch of stuff off of it. Oh well.

That's a data point but that video is an opinion stated as a fact. You'll find others who have different results. It would be nice if there was some actual research.
Has anyone calculated or measured the input lag of ADB vs other protocols such as PS/2 or USB? This is unfortunately hard to search because most references on the web to ADB are for the Android Debug Bridge.

From the numbers given, it seems like ~2ms to send a packet (my math may be off), which is quite good when compared with other contemporary/modern protocols (see: https://danluu.com/input-lag/ for examples)

It's okay. It's not as good as the SIO that came with the Atari 8-bit computers, but it's alright.