Re: Hallelujah - File Explorer's file path limit is not 256 any more !
The limit is not Explorer's. It is Win32's. It was promised (back in 1991 or thenabouts) that 260 characters would be enough for any file. This was over three lines of typing in a command prompt back then and the designers clearly asked themselves what would be a stupidly long name and then doubled it.
(There is an API work-around and so Microsoft could have written Explorer to be able to handle longer names. This would let you quietly create files that your other programs couldn't handle properly, perhaps causing a buffer overrun or a truncation-related security flaw, depending on quite how they couldn't handle it properly. Microsoft presumably thought that the ability to dig yourself deeper into trouble wasn't a great feature. I'm inclined to agree.)
Of course, some people like to put all the meta-data for a file into the parent's (and n-fold grandparent's) directory name. This is typically a crap idea because you lose it the moment you move the file somewhere else, but people do it anyway. Such people can quite easily blow the 260-character limit. The view of an operating system designer is that these people are twats and they can sod off.
I would note in passing that *any* fixed limit will eventually upset some "test suite" and that having no limit at all will eventually produce an eco-system where twats store file contents in the filename and the files themselves are empty -- just because they can.
Unix has similar hard limits, but they are generally larger and less documented. The consequences are that (firstly) Windows gets the schtick and (more importantly) the equivalent failure in Unix-land depends on what application you are using. That's not actually better.