Why doesn't Windows 10 understand Linux symbolic links?

Question

Windows

There is a joint web-project, which is being worked on by developers for Linux and for Windows.
A Linux developer creates a symbolic link from one project's (public) directory to another (not web-accessible). A Windows developer downloads a git branch update and sees that a "file" of the link has appeared in the public folder (without an extension, there is a relative link inside the text), but no magic happens, and windows does not understand that this is a symbolic link. At the same time, if you do mklink, then a message will be displayed that "it is impossible to create a file because it already exists", and if you specify some other name, then the link is created (as a shortcut) and the symbolic link starts working, but you need to both developers had the same addresses.... how to make windows understand symlink file from linux? ... it is important to note,

Answer 1

because windows knows how to work with NTFS, not posix file systems.
Chotby understood whether to use the built-in WSL or not to use Windows.
Read about how the Windows and Linux file system works, and you will understand that git will not transfer Linux entities to Windows.

Answer 2

This is no longer a question for Windows, but for the git client under Windows, which does not use all the features of the file system.

Answer 3

You don't have to force Windows to understand this. Do not use links in the project code, they are not needed there.

The purpose of a symbolic link is to make the Nginx web server understand that the address of the symbolic link is referring to files that are actually "in a different place".

If you use links on the server to switch to new versions of the code, then it has nothing to do with the code itself. If you are using links on the server to build some kind of routing, then you are clearly doing something wrong.
As a last resort, a broken link does not negate the fact that the file exists at the original path.