Lots of phones support relocking to a user provided key (OnePlus does for sure) but it's a less trusted state than locked to the vendor key, I don't think it counts as good enough for full SafetyNet
Apples to oranges, very different characteristics. WiGig (802.11ad)'s up in the 60GHz band where even the oxygen in the air is absorptive, I think most walls pose big problems. But there's 6 channels of bandwidth each with 2160 MHz of space.
Wifi by compare recently went from 480 MHz of space (5GHz) to 1600 MHz (+6E spectrum) of space available in total. Colossal gain, nearly tripled in bandwidth. But there's still less bandwidth in all wifi than there is in a single wigig channel.
That wifi is making such excellent use of such a relatively limited amount of spectrum is amazing. I'm expecting impressive connectivity even at significantly reduced link budgets.
But as for the point here, about interesting new inter-device connectivity, I agree with both of you. Wigig did have these capabilities, has had interesting video & device shipping for a while now. Alas adoption has been just critically low. VR was basically the only thing that pulled this impressive wigig standard out of the hole it had crawled in to die. No one was building this stuff. Huge loss, huge pity. I really wish we had a lot more experience using wigig like technologies, because to the grandparent posters point, having this massive connectivity capability on tap for everyday consumer & business wifi: it's definitely going to enable intense new streaming & inter-system capabilities. I just wish we'd gotten more of a chance to explore this space more freely in the past 10 years, which is about how long 802.11ad/wigig's been around for.
Sure the concept has been around, but not widely implemented. I participated in a WiGig laptop dock PoC a few years ago - it wasn’t great. Usually throwing more bandwidth at stuff helps.
That's great if you only use these drives on your big computers. Sadly if you do want a "universally" portable drive – usable on an Android phone and an iPad and whatnot – you're stuck with horrible basic filesystems like exfat :(
I think the one you are replying to understands this, but the point is that "the last few writes" may be executed in different order by the underlying hardware and this might confuse the filesystem.
Well, seems like because physics™ it's hard to do both 420W charging and 69Gbps data over the same cable. And also people want thinner and cheaper charging cables. It's still better to have a unified connector and different capability cables.
> most cables get it wrong to a dangerous degree
That was the case in the early days. These days it's getting hard to find bad cables.
> negotiation is more complex and expensive to implement as well, even if you're only doing a low-capability device
No need for negotiation in a low capability device. Two resistors. It's not rocket science. Raspberry Pi did screw up and use one resistor but they made that mistake so famous that everyone knows not to repeat it now.
Well, the argument is that versions not being speeds anymore is the problem and it would've been easier if they were. Like they are in Wi-Fi for example.
Like that, but also they keep renaming things. And when it's only two lanes max and any faster device will support two lanes, there's no reason to put lanes in the name.
Even if I'd made enough I'd make it a point to use workarounds like these to avoid the scams or inefficiencies of the overpriced CFE cards, just to make a point.
