Mac CLI – OS X command line tools for developers
github.com
github.com
The sooner you change, the better. Otherwise that is wasted brand equity for you. If you're going to work hard to build a great tool, the recognition for that should flow to a name of your own.
I'm really terrible at choosing names, so I'm sorry for criticizing more than I'm suggesting.
I wish you lots of success, the world needs more easy to use development tools. Don't let armchair quarterbacks like me demotivate you :)
A good example of my ineptitude at identifying good names.
The great thing about open-source is that everything is created through collaborarion. The best of everyone is contributed to a project in benefit of the entire community.
Or shorten it to MacCli if you must.
The actual command doesn't have to change.
What you have is a great, simple, direct name for a utility script. Better to ignore the trademark / brand FUD.
Not sure what a better name would be, but it may need to be changed. I should add though, I had no illusions this wasn't an official apple offering.
In this case, I think the author of this tool has the most to lose, because he is building brand equity for someone else. If next year his tool takes off and he is forced to rename, he has to start over.
But let's assume this tool becomes so successful that he gets away with the "name hack", then it sets the wrong example for other aspiring toolmakers: "don't bother picking your own name, surf on on someone else's and if you succeed fast enough, you might get away with it". That is the same calculation which leads less scrupulous people like Comodo and OVH to "ask for forgiveness rather than permission". I think that is dangerous for innovation because it makes it less rewarding to try something new under your own name. Why bother if someone else will reap the rewards in the end?
Everybody knows MacPorts, and there's Mactracker and MacCleanse on the App Store itself, and the infamous Mackeeper (which may very well be malware; Apple should go after them first) and companies: MacPhun and MacPaw.
But I guess people may confuse "Mac CLI" as being an official part of macOS.
Just anecdotal evidence.
Is there a way to install only the dependencies that one cares about?
And if people are in the command line often enough, they do memorize the actual commands. They really, really do.
Would you rather remember: `pmset sleepnow` or `mac restart`?
For example: mac ssh:download-folder
how in the world does it 'increase cognitive load'? Seems like its just your opinion. I know how to shut down a generic linux box. But mac shutdoown or mac reboot is still easier to type and remember.
1) It's already muscle memory.
2) It's not hard.
3) Other *nix OSs use is too.
I see this as either being used frequently enough to be easily memorized, or infrequently enough that a quick check of the man page is fine. The real benefit is that it's a very general solution that works on basically any system, and for a wide variety of commands. As another commentor pointed out, the apropos command makes this strategy even more powerful.
alias eject="hdiutil info | gawk '/^\/dev\/disk([0-9]*)\>/ { system(\"hdiutil detach \" \$1) }'"
HomeBrew screws with your systems file permissions and installs directly into the standard system directories.
MacPorts (https://www.macports.org/) is at least a good, and it installs into the /opt tree, staying out of the way of anything Apple or Darwin wants to do when updating or patching your system.
Don't like MacPorts? There's always Fink (http://www.finkproject.org/), which installs into /sw and looks like Debian (i.e. apt-get).
HomeBrew seems like the worst of the three. :-(
in contrast, i somehow couldn't manage to efficiently use macports and fink.
http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...