nostr:npub1a73wyr3s8ffagwsnlfd548d0nsaqcwdnn6550akehaxglw3kzc8qce7y6q it seems you aren't getting my point of windows being the exception, so go try running your original broken script on every modern operating system besides windows. note that it behaves the same - that is, broken. now compare that to windows, where it works. that's why windows is the exception, not the other way around
nostr:npub1yj5xannuqk0s0hz6c53mgqc4mrxpcr0rssyn4ku2ckrmtxyhjk8qwvutt3 not other way around:
I’ve just debugged my problem : module A was writing to directory Kurwa and module B was reading from directory kurwa, so naturally it worked on Windows 11 but it didn’t work on Linux
So I had to debug it on Linux first as debugging on windows useless
Discussion
nostr:npub1yj5xannuqk0s0hz6c53mgqc4mrxpcr0rssyn4ku2ckrmtxyhjk8qwvutt3 yez, Windows is exception, but it only shows that it should be tested and debugged FIRST ON LINUX because these problems can’t be detected on Windows