News for hackers. Stuff that matters.
Re:Fix 260 character file name length limitation: Declined by badman_ting on Monday October 07, 2013 @04:49PM (#6511160)
Right now, sure. But suppose some piece of software goes rogue and starts creating dirs and files. Further suppose that there's enough of them to fill the disk. OK, now your disk is full and nothing on the machine works, so you need to delete those deeply-nested files. Except, whoops!, the paths are too long, so you can't delete them with the command line. OK, now you're writing a script or burning some godawful boot CD to try to get to a safe mode or Linux kernel. All in order to delete some silly unnecessary files.

Problems like this aren't problems when everything is working normally. But that's beside the point. When the shit hits the fan and the system is only getting in your way and adding to the problems instead of helping solve them, it's really really really not fun.

Re:Fix 260 character file name length limitation: Declined by throwaway9101 on Monday October 07, 2013 @09:00PM (#6512333)
I know, when the shit really hits the fan, visual studio is the tool I would use to try and clean up those messy directories.

</sarcasm>. The complaint is about Visual Studio's decision in particular, not the weakness of (some) (old) Win32 APIs.

Re:Fix 260 character file name length limitation: Declined by barrkel on Tuesday October 08, 2013 @11:56PM (#6519302)
Or use Cygwin, limited only by the OS (32K path IIRC).