3 ms·
Even when not considering browsers - working with git server-side is a pain as it's so coupled to the filesystem. Not only you have to be careful about races, b
by exyi 6y ago
Even when not considering browsers - working with git server-side is a pain as it's so coupled to the filesystem. Not only you have to be careful about races, but also you have to know at which state is the repository at the moment. Any time a command fails, the repository is in an unpredictable state (is it a merge or what???), so the code using git has to delete and reclone...