HNHacker News
TopNewBestAskShowJobs

sfoskett

496 karma · joined November 12, 2010

[ my public key: https://keybase.io/sfoskett; my proof: https://keybase.io/sfoskett/sigs/_mnYEASq8nBqIbRfrZygetWkZRT5lQtfuK9-EY3AIOM ]
submissionscomments
sfoskett··on Total Nightmare: USB-C and Thunderbolt 3
The point is that due to the much better backward compatibility and do-it-all nature of USB Type-C, consumers are much more likely to run into incompatible devices and cables than ever before. Walk into any store and you'll see dozens of cables and peripherals that look the same but perform differently (or not at all) based on a confusing array of protocols and standards.

It's true that USB has always been a bit confusing, but now we have many, many more incompatibilities to worry about.

sfoskett··on Total Nightmare: USB-C and Thunderbolt 3
Well the USB IF does have standard naming and labels for the protocols. The issue is that USB Type-C is a cable/port standard, not a protocol standard. Makers ought to label the USB Type-C port with the highest USB speed it can handle ("SuperSpeed" or "SuperSpeed+" typically) but they don't. And Apple left the Thunderbolt icon off the ports on the new MacBook Pro! So buyers have no immediate way to know if a MacBook supports USB 3.1 gen 1, 3.1 gen 2, or TB3. (hint: gen1)
sfoskett··on Building the next generation file system for Windows: ReFS
If ReFS is really in the Server version of 8, and if it really doesn't support sparse files, consider the implication of built-in deduplication. It does sparse files at a layer above the filesystem, along with dedupe and compression. Or, as mappu points out, ReFS could assume it's running on VHD/CSV, punting those features to a lower level.

Perhaps Microsoft is making a decision to focus the filesystem on being a simple storage engine and moving features into other modules (primarily) above or even below it?

← PreviousPage 2 of 2