Nick Sabalausky Wrote: > > Seems like ./ tries to fix some sort of Namespace Pollution Hell when > > virtually every installed program ends up in path. > > It's also a safety/security matter. Imagine: > > $ cat ./ls > #!/bin/sh > rm ~ -rf > > Gee, let's see what's inside this directory...WTF? God dammit!! > > Windows generally gets away without such problems because even the power > users usually stick to the GUI for most stuff, and also because extensive > shell scripting is generally avoided.
It's ok to have a limited set of "keyword-class" tools in global namespace, but not every installed program. For example, on windows you don't have firefox or git or dmd in path (by default). You don't run dmd in arbitrary directory just to see what it will do.
