News for hackers. Stuff that matters.
Re:Why USB sucks (2005) by moron4hire on Friday April 25, 2014 @06:02PM (#7649294)
#1 is just the nature of cables. If you think blutooth is the answer, try using blutooth for a while.

#2 is actually a really big deal with developing software to interact with anything USB. Well, I should say anything based on the FTDI chipset. I don't have any experience with anything else. Which is increasingly the case, given the modern proliferation of hobbyest hardware projects. There are no connection status events. RS-232 never developed any because a loss of connection with a cable that is physically bolted into the computer should be a catastrophic event.

Oh, I cannot tell you how many hours of my life I'll never get back debugging connection status issues. And it doesn't necessarily have to be a physical break in the connection that causes the problem. It could be an every so small short in the connector that only triggers once in a blue moon when you shift yourself in your seat and accidentally bump the wire with your chair handle while also plugging in your headphones.

Luckily, the latest versions of Windows (don't look at me, clients don't seem to care that they'd save a ton of money using Linux) are pretty robust to USB connection cycles. It used to be, if you lost a connection before closing the connection, you wouldn't be able to close the connection. The USB device would get assigned to the same COM port, which you couldn't open, because you still had it open. But couldn't close. Because you lost the connection. In the later days of XP, it often led to having shutting down the program, recycling the USB connection, and start the program again. In the early days of XP, it required a whole system reboot.

#3 I don't actually begrudge anymore. It's a situation that occurred due to evolution. Regular B connectors are too big for small devices, so Mini-B was developed to accomodate. But it turned out that the design was significantly flawed, creating a board connector geometry that was not very robust against repeated pluggings and unpluggings. Micro-B was developed to be significantly stronger, to support a greater number of cycles (if you look closely, they aren't just a different shape, the pins are set in the plug completely differently). Then smartphones turned into micro-microcomputers and people started to want to plug devices into them. Suddenly, what was strictly a slave interface before, needed to have the option to become a master interface at will. USB-OTG was the result, and it's actually a rather clever compromise that maintains backwards compatibility well.

#4 can be a significant problem when doing any sort of real-time data collection. It's nearly impossible to connect a variety of sensing devices to a PC and be able to synchronize the readings of them in time. For the most part, I take the system timestamp for everything, then generate a best-fit curve and use that for my calculations. There's just no confidence in the precision of the time resolution in USB.

#5 isn't USB's fault, it's device manufacturers. Hardware developers are some of the worst programmers in the world (and yes, they will say the same thing about programmers and circuit design, but you don't see me designing circuits, now do you?). Your printer has a really shitty system for installing drivers because the driver developer can't be arsed to learn how the operating system works with drivers. And he can't be arsed because his manager is probably bugging him to "get back to real work".

His list of new problems are largely obviated by FTDI. However, FTDI has its own problems, both technical and political.

Re:Why USB sucks (2005) by Peaker on Friday April 25, 2014 @06:21PM (#7649405)
Micro-USB has been terrible, reliability wise. The ports survive pretty well, but cables wear out at an unacceptable pace.

I buy stocks upon stocks of micro USB cables, and I've switched to wireless charging, because I simply keep running out of them.

It's not simply me being reckless, my wife's cables wear out, as do my brother's and various friends.

Also, none of us had any of these issues back with mini-USB (though admittedly we used those cables much less than we use micro today).

Re:Why USB sucks (2005) by jackalope on Friday April 25, 2014 @07:07PM (#7649646)
I agree. Micro USB was not an improvement over Mini USB. I've never had a Mini USB cable go bad, but easily a third or more of Micro USB cables I've owned are faulty, with barely any stress. Also, Mini USB cables were a huge improvement over standard USB, because I could orient them by feel alone. I've lost that ability with Micro USB, where it often takes three tries to plug it in.
Re:Why USB sucks (2005) by secabeen on Friday April 25, 2014 @11:24PM (#7650307)
That's all intentional. Mini USB cables were stronger than Mini USB ports. Its generally better to make the weaker side of a connector the cheap easy-to-replace cable.
Re:Why USB sucks (2005) by adwf on Friday April 25, 2014 @07:12PM (#7649664)
I've had a bit of luck with Amazon Basics branded cables recently. They've got quite a chunky connector/cable that's lasted a lot longer than my default phone cables have.
Re:Why USB sucks (2005) by 7952 on Friday April 25, 2014 @07:12PM (#7649665)
If stress is placed on the connector something will break eventually. From Wikipedia; [it is] designed to reduce the mechanical wear on the device; instead the easier-to-replace cable is designed to bear the mechanical wear of connection and disconnection. Compare that to 3.5mm audio sockets where the device has to be fixed instead of the cheaper headphones.
Re:Why USB sucks (2005) by lelandbatey on Friday April 25, 2014 @08:17PM (#7649888)
Interesting. I've owned devices that are exclusively micro-usb for years now, and I don't think I've ever had a cable wear out on me. However, that may be because I lose them to quickly for them to wear out.

When you say the cable wears out, do you mean the plastic-encased wire wears out, the male connector wears out, or the point where the male connector is joined to the wire wears out?

Re:Why USB sucks (2005) by Peaker on Saturday April 26, 2014 @06:51AM (#7650976)
The male connector wears out, I think. But maybe it's the wire side of the male connector, I've never thoroughly tested, just played with the angles till it charged.
Re:Why USB sucks (2005) by ewoodrich on Friday April 25, 2014 @06:33PM (#7649476)
Does the connector have much effect on the construction of the cable itself? Perhaps Micro-USB cables are more likely to have a thinner cable due to the smaller connector.

What I have experienced are the connectors on the cable either breaking or ripping off of the cable. This has happened twice with a device I use regularly, with no damage whatsoever to the port.

Re:Why USB sucks (2005) by Peaker on Friday April 25, 2014 @06:46PM (#7649535)
The cables die because of the connector. You can toy with the connector and it does work in some angles after it breaks, most of the time.
Re:Why USB sucks (2005) by analog31 on Friday April 25, 2014 @06:51PM (#7649566)
What are the problems with FTDI?

I don't do high speed data collection per se, and wouldn't know how to do it on a desktop platform even if the issue of synchronizing the ports were licked. So I shove real time functions to an outboard micro that does run in real time.

FTDI has been the best thing since sliced bread for me. It has proven to be remarkably robust and portable in my use.

Re:Why USB sucks (2005) by fdkz on Friday April 25, 2014 @08:14PM (#7649880)
One example: when the usb cable is yanked under macosx while a serial port is open, 50% of the time macosx crashes, and sometimes the crash occurs randomly up to 2 hours later.
Re:Why USB sucks (2005) by X-Istence on Friday April 25, 2014 @09:34PM (#7650057)
That's because the Mac OS X FTDI drivers that FTDI provides are absofuckinglutely terrible. Don't install them, use libusb from userspace...
Re:Why USB sucks (2005) by duskwuff on Friday April 25, 2014 @11:44PM (#7650359)
Or use the less-buggy FTDI drivers that are provided by Apple in Mac OS X 10.9. The vendor drivers are no longer needed.
Re:Why USB sucks (2005) by X-Istence on Saturday April 26, 2014 @03:58PM (#7652571)
Did not know that Apple provided drivers, finally! I haven't played with an FTDI in a while!
Re:Why USB sucks (2005) by thmorton on Friday April 25, 2014 @06:13PM (#7649357)
> #2 is actually a really big deal with developing software to interact with anything USB. Well, I should say anything based on the FTDI chipset. I don't have any experience with anything else. Which is increasingly the case, given the modern proliferation of hobbyest hardware projects. There are no connection status events.

This is more of a Virtual Serial Port driver issue than an USB issue, right? USB itself always seems pretty good about connect/disconnect events (at least on Linux). However, the FTDI drivers which detect this don't have any way to pass it back to devices reading the COM port (because of RS-232 legacy, as you said).

However, for real USB devices (not FTDI/VCOM), connection event notifications shouldn't really be an issue. Yes, annoying to deal with, but at least you can detect it, unlike with serial...

Re:Why USB sucks (2005) by nitrogen on Friday April 25, 2014 @09:05PM (#7649978)
RS-232 has signals for device detection, but they are optional.
Re:Why USB sucks (2005) by XorNot on Saturday April 26, 2014 @03:51PM (#7652545)
Which still makes it a bit of a mystery why you wouldn't emulate them, since USB plug/unplug maps 1:1 to that signal.
Re:Why USB sucks (2005) by lucisferre on Friday April 25, 2014 @06:48PM (#7649552)
I use Bluetooth every day with my keyboard and mouse. Generally speaking it's problem free. Although I also use it for other things like my headset where I agree it's a pain. Seems to depend on the implementation of the pairing.