On the technical side of things, ADB is NOT hotswap nor was it ever designed to be.
The ADB table is normally only initialized with data from devices at startup by the ADB manager. A reinit can be forced (there are utilities for this), but it is not very clean and can cause issues on a running system.
The ADB table contains a list of every device connected to the system ADB bus and unique ids. by hotswapping, it is possible (usually, but not exclusively, with devices that have custom drivers beyond the basic apple keyboard/mouse) to create issues with data being sent to the wrong spot in the device table if the devices don't re-enumerate in the same order.
Also, in general, there is no hotswap circuit protection required in adb devices.
Once upon a time I had a friend who insisted that his ISA cards were hotswap, they just needed a restart after you put a new card in a slot or they wouldn't show up. Same general logic. ADB is a rather simplistic bus, but it has no provision for being truly hotswap.
The ADB table is normally only initialized with data from devices at startup by the ADB manager. A reinit can be forced (there are utilities for this), but it is not very clean and can cause issues on a running system.
The ADB table contains a list of every device connected to the system ADB bus and unique ids. by hotswapping, it is possible (usually, but not exclusively, with devices that have custom drivers beyond the basic apple keyboard/mouse) to create issues with data being sent to the wrong spot in the device table if the devices don't re-enumerate in the same order.
Also, in general, there is no hotswap circuit protection required in adb devices.
Once upon a time I had a friend who insisted that his ISA cards were hotswap, they just needed a restart after you put a new card in a slot or they wouldn't show up. Same general logic. ADB is a rather simplistic bus, but it has no provision for being truly hotswap.