The USB organisation will no longer use the SuperSpeed and USB 4 names.
Click here to post a comment for The USB organisation will no longer use the SuperSpeed and USB 4 names. on our message forum
Venix
Wait is it just me .... Or the naming now is crystal clear ??? I was not expecting that kudos !
Neo Cyrus
Venix
Loobyluggs
About god damn time.
turbare
So USB 2.0 is the High Speed one referenced in there?
Crazy Serb
Did someone at USB-IF got hit in the head?! This is definitively not normal for IT standards...
I hope others like VESA, nvidia and AMD to follow. Not sure about intel naming shenanigans.
Alessio1989
I don't see USB 10Gbps cable :V
Mda400
To the point and no 3.1 /3.2, 2x1/2x2 fluff.
If I want a 20 gbps cable that can charge my laptop, all I have to look for is that 20gbps logo with 60w.
mackintosh
A bit late, but better late than never. Any change that will make this clusterturd clearer is welcome.
schmidtbag
Or y'know... they could've just stuck with a more sensible number for power delivery and bandwidth that all host devices and cables could be expected to provide, thereby making it actually universal. It's such a shame because there is so much potential to make it a great interface.
rl66
And when they will do a revision, like in the past, will it be "USB 40 Gbps 2" or will it "USB 45 (as an exemple) Gbps" ... lol
More on topic, it should have been like than since the 1st USB as all type A and B look the same from 1 to 4.
tsunami231
less confusing now i guess the wattage packaging and cable look confusing which is 240w and 60w? according to this all cables cappable of 240w and 60w? or is there 240w and 60w verisons of these cables
atlest lest there is not more 3.2 superspeed 10gbps and 3.2 superspeed 20gbps.
Naming it USB1/2/3/4 etc would been fine if every time there was new verison and the speed increase they just upped the number by one
geogan
Yeah... the Gbps is clearer, but I never heard of the wattage rating... didn't know there was a 60W and 240W version of cables with same speed??
mackintosh
There are, it's a complete mess. Previous iterations also had these issues.