Re: Hang on a mo ...
Your complaint about mount points might be valid but I have my doubts. I can't think of anything about an NTFS volume that requires it to be treated as a self-contained volume. Windows links can link any folder structure anywhere so you can make 'D:\' appear under c:\Mounts\ if you wish (I actually do that on my development machine). I also think that assigning a drive letter to a volume is optional so I think you can indeed mount an NTFS volume under an existing folder structure just like you can with Unix variants.
Also I suspect that there are components of the file system that are physically fixed in place on a disk.
No. Only the boot sector which is fixed at LSN 0 (possibly also the recovery boot sector at the other end of the volume). Everything else can be anywhere else within the volume. The boot sector specifies the location of $MFT (Master File Table) and everything else (including $MFT) is a file whose location is specified by a record in $MFT.
Its difficult to resize a NTFS partition and may be the reason why disk performance (along with Windows) performance drops off over time.
What difficulty? The DiskManager can do it in a couple of mouse clicks. Extend the partition. Grow the volume. If no space to extend partition, span the volume onto another partition. The only structures that might have to move are the recovery boot sector and $MFTMirror which have to be moved if you shrink the volume (because they are normally placed at the end) and could be left in place if you grow it but which MS might recommend are relocated to the new end-of-volume.
Any drop-off in performance can be attributed to the usual OS-agnostic reasons: Software installation and disk fragmentation. On the latter front I will say that NTFS doesn't do much to avoid fragmentation - HPFS went to great lengths to do so. But then in my experience no file system was as determined as HPFS to keep files contiguous so I suspect that NTFS is no worse in that respect than any other OS.
System performance slow-down, yeah. Maybe. Can't say I've ever noticed it nor attempted a side-by-side comparison. Maybe it's like the old 'boiling frog' thing :)
But we can't blame NTFS for that. I'd say blame users for installing random crap on their machines and - possibly - software publishers for writing shitty code and being lazy in clean-up.