Since it has been adopted by the USB Implementers Forum (USB-IF), it is by definition not "a Apple proprietary standard", is it?
USB IF, by the way, publicly showed off the new connector standard early last year.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
John Gruber: Apple Invented USB Type C
- Thread starter MacRumors
- Start date
- Sort by reaction score
Since it has been adopted by the USB Implementers Forum (USB-IF), it is by definition not "a Apple proprietary standard", is it?
USB IF, by the way, publicly showed off the new connector standard early last year.
You can have all the error detection you want built into a protocol but if the physical link is not there, the error cannot be corrected and the target file(s) will still be silently corrupted.
Ever notice how any media which carries a lot of data at high speed almost invariably has a physical means of securing the cable regardless of the underlying transmission protocols? RJ45 has clips, coax/twinax screws in, various fibre connectors such as LC or ST clip in and sockets sometimes even have further physical protection from accidental disconnection (SFP etc).
USB with only friction holding it in is insecure enough as it is, adding in a magnetic component which is designed to disconnect is insanity.
Last edited:
Lessee...
- Not really needed for a device designed to spend most of its working time un connected.
- Getting ready to deal with EU legal requirements that, in effect, "everything electronic that can be recharged has to use a USB connector" coming up in the next year or two. Apparently Lightning won't do over there.
Uhhh. FireWire (IEEE.1394) is a standard. Not to mention that it's had a pretty good run, going on 20 years now. (There's more to life than consumer electronics.)
----------
Pity about all those laptops on the market that don't have such a power connector, isn't it?
Apple worked on FireWire for several years before IEEE (not to mention TI and others) got involved.
And it's not quite dead yet, if "living" doesn't involve consumer electronics as much currently. It's still used in automotive and aerospace applications.
You definitely are not and that's the one reason I wouldn't be able to get the new Macbook.
I would argue that most of the people here being critical of this decision are doing so because they care.
Like Ethernet, miniDisplayPort, miniDVI, USB, FireWire, ThunderBolt, NuBus, PCIe, ... standards like that?
You forgot to add the /s?
It's also still in modern products. My Cooler Master HAF 932 (although it's a few years old, it's still sold) has a FireWire port. Unfortunately, I have no way to use it so it's just a dead port.
Good point! Not sure why everyone was calling it "USBGate" which is kinda generic. We should start calling it "CGate" instead so that Seagate won't sue. Or I guess if you spell it "SeaGate" then it may be okay due to the capital "G".
Although there's that, given the EU regulations it seems fairly likely that it will change fairly soon.
The EU is requiring USB for connecting/charging consumer electronics in the next couple of years.
Might be some connection here.
They don't need to since it's a standard now and anyone can use it basically.
----------
Smaller by how much? Isn't USB-C fairly close to microUSB as far as size and that is fairly close to Lightning?
There can always be corruption but not silent corruption. I don't know if it would be efficient enough, but there is always a way to detect those errors. Edit: Of course, if it's very inefficient, it's not useful.
If you send the hash code of the data before sending the actual data, the only way for that to get silently corrupted would be for the hash to be corrupted and, by miraculously bad luck, have the corrupted data sent through match that corrupted hash.
I agree with everything else you said but issues with data transfer can easily leave corrupted or incomplete files. Error detection in transmission protocols is at the bit or packet level (I don't know enough about USB to be specific) and has no means of detecting an incomplete or damaged file. You can just be assured that every bit which did get transmitted is correct, but it doesn't ensure file integrity. This kind of thing would need to occur much higher in the stack than the physical link since there is no awareness of even the concept of a "file".
Yes, you're right my comment about error correction was too general. One needs error correction at every level of the stack. As for example a browser downloading a file over a network knows that networks are more susceptible to interruption than reading a file from disk and thus applies more error checking on the former.
It's nice to have a keyboard if you actually have something to say via email. Some folks don't want a separate keyboard they have to remember to bring along.