Live data from Hacker News

M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

eclecticlight.co

171–180 of 333 posts

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#171
post #48

Earlier quoted context omitted.

> USB 3.1 Gen 1 is the straight rebranding of USB 3.0 Why? To solve what exactly? In a sane world, it'd be major.minor, with nothing appended at the end. Allowing marketers to take over everything was such a terrible mistake. At this point I myself just don't differentiate USB versions beyond 3.0. 2.0 is the slow one, 3.0 is the fast one, anything newer is "so fast I won't ever saturate this much bandwidth anyway". T…

Tricking people into buying new hardware while incurring zero marginal cost of development, sales, distribution? Sounds like a winner. /s

To save tech nerds who know the difference from unnecessary expenses. Let others spend more money into the economy. Win for us. /smirk

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#172

Quoted post unavailable.

All gripes I don’t have, and my m1 max is a kickass laptop, expensive but you get what you pay for. And I have quality. Reliable, clean and fast, both on the software and hardware side.

We've got ~100 engineers in our company and there are essentially two categories of engineers: the ones that are enjoying their M1s and those who are looking forward to moving from Intel to M1.

Admittedly that's still pretty anecdotal. It's not like each one of those engineers has rigorously tested all alternatives.

But still, no complaints and people are loving the battery life and lack of heat.

The dongle situation is unchanged from 2016-onward Intel Macs and has been resolved with the latest MBP models. The dongle situation was absurd but never thaaaat bad; you just had to buy a $70 dock dongle thingy.

Single external monitor support on the lower-end models was lamentable, but also not a dealbreaker in an era of ginormous 4K displays.

Lack of M1 support in software is almost a non-issue. Rosetta emulation is so fast that nobody notices or cares. The only exception has been our Docker-based stuff; took some massaging to support the new arch.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#174

Earlier quoted context omitted.

Didn't last long, haha, the new one is 6E.

That one is at least a little more understandable, same phy, just operates in a different spectrum.

I guess my point is it's meant to be a consumer marketing name - and if I have to explain to them that "6E" has an "E" because it's the "same phy, but operates in a different spectrum" then they've failed to create a rational naming scheme yeah? Don't get me wrong, I get it. But I also get USB 3.2 Gen 2x2

Like ... why "E" of all letters?

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#175

The inability of the USB standards body to stick to a versioning scheme beggars belief: what in the world could "USB 3.1 Gen 2" possibly mean? Versions are free, why not simply name it "USB 3.2" and make the next one 3.3? "Gen 2" strikes me as the "Essay FINAL (final version 2).docx" of standards revisions.

> what in the world could "USB 3.1 Gen 2" possibly mean? Versions are free, why not simply name it "USB 3.2" and make the next one 3.3? USB 3.1 Gen 1 is the straight rebranding of USB 3.0, USB 3.1 Gen 2 is the "original" 3.1, which is 3.0 updated to a 10Gbps signalling rate (from 5), and a more efficient encoding (128/132, versus 8/10). But wait, there's worse! USB 3.2 Gen 1 is the same thing as USB 3.1 Gen 1 USB 3.2…

Clear as mud.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#176

The inability of the USB standards body to stick to a versioning scheme beggars belief: what in the world could "USB 3.1 Gen 2" possibly mean? Versions are free, why not simply name it "USB 3.2" and make the next one 3.3? "Gen 2" strikes me as the "Essay FINAL (final version 2).docx" of standards revisions.

The naming seems strange but the idea is sound, right? Perhaps they should have picked a different marketing name for each of the Gens. Anyway, it's like how we have: C++ 17 map and C++ 17 unordered map. Different functionality is specified in the same versioning standard.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#177

Earlier quoted context omitted.

The fact that I can't connect more than one monitor to my M1-based iMac is a fucking travesty.

Why can't you? I am typing this from an M1-MPB with two monitors. I just have 1 through thunderbolt and 1 through the hdmi.

I have a "MacBook Pro (13-inch, M1, 2020)" and I clearly can't have 2 external monitors. I tried everything.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#178
post #147

Earlier quoted context omitted.

Isn't the Mac M1 mini $699?

Did you just compare the $700 Mini to a $140 ECS Liva or some $200 HP or Asus Chromebox?

Did you just compare a $200 HP or Asus Chromebox to a $0 free 15 year old Dell tower from your local Freegeek?

We can do this all day.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#179
post #78

Earlier quoted context omitted.

Sadly this might be more user friendly then the current setup. Even just a bit vector of the capabilities, expressed as a decimal or hex number, would be more comprehensible.

You would then get USB Type 61513 port and USB Type 48757 device, which could only communicate at Type 45151.

Yes you would. But that doesn't mean you can't represent it with 16 nice graphics that clearly show if something is supported or not.

Re: M1 Thunderbolt ports don’t fully support USB 3.1 Gen 2

#180

Earlier quoted context omitted.

I think the should really just use sha hashes of the standard document, to avoid all this version name issues.

I think they should use the Chrome/Firefox numbering system. Every time you put out an update that's big enough for users to be affected, increase the integer by one. It's the most intuitive system to humans.

The Chrome/Firefox numbering system is “new number every month”. Most of those updates don’t bring any new notable features.
Post reply on HN