Is there an actual issue that arises because of the fact that currently it uses forward slashes? I believe I already fixed the issue with duplication inside the $PATH

It causes problems when using an application or script to normalize and deduplicate the Path environment variable, which unfortunately is necessary because many other applications also don't properly check if the path has already been added. So when doing that normalization before the dedupe, then running bob after, bob will just add the path again with a forward slash even though it's already there with a backslash.

That's the exact scenario I ran into. Also, Windows doesn't really like forward slashes in the Path environment variable. If you try to edit it in the settings and there's a forward slash in the path, it will complain that the forward slash isn't an allowed character and won't let you save it.

hmmm i see