How to make a symlink to a folder so that the program does not notice that it is a symlink?

Question

linux

For some reason, the program starts to work incorrectly if, instead of the usual data folder, it slips a symlink to this folder.How to make the program not notice that this is a symlink?
The question applies only to Mac OS (everything works on Windows).
The roots of the problem can be found in my other question: How to solve the problem with Sencha Cmd [WRN] Aliased resource: file?
Additional question: is it possible to make Junction Points on the poppy? It arose due to the fact that there is no problem on Windows if you use Junction Points.

Answer 1

A simple explanation of symbolic and hard links
Apparently you need to understand all the options:
Hard Links
Junction Points
Symbolic Links

Answer 2

Junction Points is a feature of NTFS, but under Unix, as a rule, there is another f.s. used. So either NTFS or nothing.
Hard links don't work either?

Answer 3

I doubt that there is no NTFS support on the Mac, if so, why not install a full-fledged Windows in a virtual machine, give direct access to the disk and do whatever you want, why not? And the wolves are full, and the sheep are safe. Most likely, only the junction point will be suitable for your purposes, because hard links that slip through the comments are a completely, completely different story ...
There is data on the disk, let's conditionally call it "12345", and there is, so to speak, the "name" of the file, data-bound, "My Photo". Hard links allow you to designate without duplicates that the created file "Me and the cat" is equal to the data "12345". As a result, we have two files with different names, but occupying the same disk space. For obvious reasons, this does not apply to folders, folders do not contain anything in the sense of data,
Junction points differ in the mechanism of operation. In some ways, they are similar to hard links, but they allow the system to say that this folder is equal to another with such and such files. The two tools, hard links and junction points, are implemented by the file system itself, so they are much more reliable and better to use than symbolic links implemented at the operating system level.