NTFS does support them, however. Is Git just not supporting them properly?
1. You run into it, go "AH, wow, okay, I'll enable Developer Mode"
2. It still doesn't work, you're confused, you Google around a bit more and find out actually you also need to use a Git config option
3. You retry, now the symlinks work, but your compiler fails because "Destination Path Too Long", huh, that's weird
4. You google a bit more, and discover you need to set a registry option. So you do it, but you still get that error..
5. You discover there's another Git option you need to set
And then you're like, hey, what was I doing again? Where did the last hour of my time go? It's death by a thousand paper cuts.
My understanding is Microsoft's concern is that applications and OS components not expecting them could lead to security issues. Not sure how real that concern is, but that's the excuse I've heard.
Bufferoverun I guess? I haven't programmed Windows in years, but there's plenty of code I've seen that is pretty much
char path[MAX_PATH];
res = some_func(&path);
https://docs.microsoft.com/en-us/windows-server/administrati...
Asking because I doubt e.g. my mom knows that NTFS has symlinks.
https://docs.microsoft.com/en-us/windows-server/administrati...
One is even a professional AAA DirectX gamedev.
I think you misread that line.
I think they misread the line.
(Whether it was right or not, so you don't need to tell me anything about that.)
From my point of view, even when someone is on the correct 'side' of an argument, if they got there by mistake it's still important to point that out. Both fortran77 and CoastalCoder can be wrong at the same time.
Is "I think you misread that line" far ruder than I thought it was?
...surely "I doubt my mom knows" wasn't supposed to be a developer anecdote that I misunderstood massively?