The thing ok can do what make can't, is work on the current shell. With ok, you can: * navigate to another folder/directory * set an environment variable I us

The thing ok can do what make can't, is work on the current shell. With ok, you can: * navigate to another folder/directory * set an environment variable I use both make and ok. For me, if I want to "make" stuff, I use make (compile, sign, zip, deploy etc.). The ok-files, I use for ad-hoc stuff, like viewing log files). It's also a good command's I can't seem to remember. A bit less structured. So I guess it's not only a technical difference, but also a slightly conceptual difference. I must say I do have a lot of (rather) small git-repo's I work on. And not every day. So when I switch to some kind of project, it helps me work faster. But your situation might differ...