But I don't agree ReFS is in the same boat. ReFS, at least as it exists today, has more in common with Plan 9's Fossil/Venti than anything else. Most notably, it explicitly doesn't support alternate streams, which is the exact piece of NTFS that is most like BFS, nor does it support extended attributes (the vestigial HPFS-era predecessor to alternate data streams). Given that it also lacks things like hard links, file system transactions (N.B., this is database-like transactions for a collection of file system operations, not traditional file system journaling), and a bunch of other things that I associate with BFS-like everything-is-a-database file systems, I don't think that comparison is apt.
Windows Server 2012 R2 and Windows 8.1 add additional
features when using ReFS, including alternate data
streams [...]
http://en.wikipedia.org/wiki/ReFS (bottom) and http://technet.microsoft.com/en-us/library/hh831724.aspxReFS features are still evolving and like NTFS is designed to be extendable (as has happened with NTFS).
It is of course NTFS that was involved in all the history of WinNT, Cairo and WinFS and still is the major FS. (I just mentioned ReFS for completeness)
Neither NTFS ADS nor Apple'S Resource fork and HFS+ ADS are something new: http://en.wikipedia.org/wiki/NTFS#Alternate_data_streams_.28..., http://en.wikipedia.org/wiki/Fork_(file_system)#Apple and http://en.wikipedia.org/wiki/Resource_fork
And neither the Explorer shell nor OSX Finder expose it as GUI - what a shame.
dotNet API's lags behind WinAPI, so dotNet/PowerShell just catches up a bit - nothing special.
Windows 9 will be interesting indeed. But I have my doubts... given that Win Vista had the advanced search dialog in Explorer shell. The newer Win 7 had no such dialog and generally the whole metadata idea was buried away in the slightly changed UI (removed list-group bar, changed metadata bar, folder doesn't remember state, custom added columns not saved, etc.) Even the great "Photo gallery" application has a optional download as part of their LIVE apps and Media player hides the playlist with its star-rating by default, etc. I don't comment Win 8.x.
I disagree with you blowing off the significance of ADS support showing up in PowerShell. You could already access ADS in .NET, but PowerShell it's interesting to see native cmdlets in PowerShell for working with ADS because it's the shell. To me, this indicates that Microsoft is anticipating developers will want to directly work with ADS from PowerShell, and that is interesting to me.
OSX Finder "information window" with its metadata feature stayed almost the same since OSX 10.4 Tiger which also marked the introduction of Spotlight desktop search.
The command line shell of WinNT, the Win32 console implementation is a bit complex (http://en.wikipedia.org/wiki/Win32_console ). Win 7+ ships with at least 3 shells: cmd.exe and PowerShell as well as the GUI shell explorer.exe (+ shell32.dll).
ADS (called Zone.Identifier) are added by Internet Explorer and recently by other browsers to mark files downloaded from external sites as possibly unsafe to run.
Notably, while all of the above use resource forks, they're not exposed to the user directly as resource forks, but rather as additional Finder widgets and behaviors.
It's ironic that Windows XP exposed the ADS in the file property dialog "summary" tab: http://www.infosecwriters.com/texts.php?op=display&id=53
Vista onwards one can only view (also in XP) and edit metadata for supported file formats like jpg, doc, docx, mp3, etc. Such formats have its own metadata format like ID3 for mp3 and EXIF/IPTC/XMP for jpeg that explorer.exe and windows media player support.
OSX uses ADS or sidecar files (on FAT/NTFS/network) but only supports 7 colors that can be mapped to tags (mean on every PC different things; similar to MS Outlook tags). http://en.wikipedia.org/wiki/Sidecar_file
Seeing the OSX sidecar files is really annoying (beginning with a dot and have otherwise the same name as the original file) on Windows. (a bit similar to the thumbs.db) The same goes for WinNT6+ that creates multi GB preview cache-database files in the users directory instead of one "thumbs.db" per directory - ultra annoying :(
It would be great, if Microsoft and Apple could agree on a new metadata sidecar standard (like XMP from Adobe, now ISO standard: http://en.wikipedia.org/wiki/Extensible_Metadata_Platform ).
My proposal: One zip file containing all XMP metadata sidecar files and file preview pictures of the current directory.
Similar to Bill Gates vision of Information at Your Fingertips with the later Microsoft's Cairo project and even later WinFS (both vamporware) http://en.wikipedia.org/wiki/Cairo_operating_system, http://en.wikipedia.org/wiki/WinFS
Microsoft's NTFS and especially its newer ReFS (http://en.wikipedia.org/wiki/ReFS ) are conceptually similar to BFS. The missing piece is a layer above the kernel driver that would have been WinFS - a shell integration and search API.