3 ms·
There's a right way and a wrong way to transition to a new interface technology. The right way is to offer the new interfaces as options or have them be there
by pmoriarty 9y ago
There's a right way and a wrong way to transition to a new interface technology.
The right way is to offer the new interfaces as options or have them be there in addition to the legacy interfaces. That way people with peripherals that are only compatible with legacy interfaces can still use them, while allowing early adopters to use the new interface.
This is what happened when the USB standard was released. Computers were sold with both USB and the old serial/parallel ports. It took many years to get to the point that serial and parallel ports were no longer standard: well, after most every consumer had already switched to using USB for just about everything.
The wrong way to go about this is what's happening in this instance, where a widely-used legacy interface is being completely ignored in favor of a new interface that has relatively little adoption.
No wonder so many consumers are upset, and that doesn't even touch issues like DRM and the analog hole, where non-DRM-forcing legacy interfaces are clearly better for the consumer.
- tunap 9y agoHeh, to be devil's advocate, sorta, we have had BT option for 17 years or so. The problem is, BT audio quality is sketchy, seamless connections are hit/miss, interference &, my fav, waning battery life. My question to those who would take the jack away is: why would I want to exercise $50+ option that is dependent on batteries when a $5 always reliable option exists? Probably the same reasons the h/w keyboard went away: profit, elegant fragility & control.
- pasbesoin 9y agoAkin to my thinking. Bluetooth still sucks. In terms of connectivity, it is in no way comparable to the seamless functioning of the older port. The data rate has required compression that screws with the signal quality, and then there are the latency issues. If Bluetooth was "great", everyone would already be using it. They aren't. Ergo, it's not time for the "legacy" port to go. I am also concerned about the push to end-to-end digital delivery. Which also gets DRM-ed up the wazoo. Sorry, I don't agree that whoever's coding up whatever implementation gets to determine my usage rights based upon their private project, implementation, and incentives as opposed to my actual, legal rights (which their lawyers are simultaneously busy trying to erode).