Re: Future proofing size constraints
Using this idealized approach, early MS-DOS wouldn't have had 32M limits either. It'd be unlimited, with IIDs for sectors and so on, unlimited length filenames, no file size limits. And it should finish booting in about six weeks from tomorrow... to an unusably slow state.
Sometimes limits aren't failures of foresight, they are CONSTRAINTs arbitrarily and artificially put in place by designers or implementers in order to make an unbounded problem more tenable, or to make it possible to solve given the practical limits of the typical consumer's hardware.
And if all that failed, you could always still pick NTFS, which had far fewer constraints at a higher performance and RAM penalty.
Biting the hand that feeds IT
