Live data from Hacker News

Mac CLI – OS X command line tools for developers

github.com

41–50 of 75 posts

Re: Mac CLI – OS X command line tools for developers

#42
post #11

I would advise finding another name for the tool. 'mac' is an obvious trademark infringement and it's only a matter of time before Apple lawyers come knocking on your door. Honestly I find it uncool to piggyback on someone else's brand in this way. The protagonists are different but it's the same fundamental issue as the "Ubuntu vs OVH" and "Let's Encrypt vs Comodo" stories we've seen recently.

Thanks for your advice! Do you have any suggestion regarding the name? I'd love to hear some ideas.

Mackly -- sounds like "Mac CLI", and has personality. tho have not googled for collisions

Re: Mac CLI – OS X command line tools for developers

#44
post #20

Earlier quoted context omitted.

Off the top of my head, I think "MacFoo" and "WinBar" are well-accepted conventions for tools built for the mac and windows respectively. Maybe look for something short and sweet in that vein? Or just something short and easy to memorize. 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 l…

If MacFoo and WinBar are OK, then surely "Mac Cli" is OK. Or shorten it to MacCli if you must. The actual command doesn't have to change.

I agree with you, plus the command name is really easy to remember.

Re: Mac CLI – OS X command line tools for developers

#45

Earlier quoted context omitted.

If you have any suggestion regarding the name, just let me know! I am open to receive suggestions about that. Thanks!

I think you should name it Mac CLI. If you really think it is an issue just call it MaCLI.

I was going to suggest the same name.

Re: Mac CLI – OS X command line tools for developers

#46
post #11

I would advise finding another name for the tool. 'mac' is an obvious trademark infringement and it's only a matter of time before Apple lawyers come knocking on your door. Honestly I find it uncool to piggyback on someone else's brand in this way. The protagonists are different but it's the same fundamental issue as the "Ubuntu vs OVH" and "Let's Encrypt vs Comodo" stories we've seen recently.

There is other non-Apple software that has been happily using "mac" in its name for a long time, no?

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.

Re: Mac CLI – OS X command line tools for developers

#48

What's so wrong with the regular command line commands for most of this?

Most people don't memorize the commands for all of these, and googling for them everytime gets old.

So instead of not remembering "tar xfz", you can not remember "mac tar:extract"? Either way, I guess you'll just end up asking google and google will tell you to use tar.

Re: Mac CLI – OS X command line tools for developers

#49
post #15

Earlier quoted context omitted.

I don't have any suggestions, but will be happy to send them if I think of anything. 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.

Thanks for advice, and if you think of anything about the name just let me know!

Apple_$eed

Re: Mac CLI – OS X command line tools for developers

#50
post #38

Earlier quoted context omitted.

man . And if people are in the command line often enough, they do memorize the actual commands. They really, really do.

man pages don't really solve the discoverability problem.

Isn't that what apropos is for?
Post reply on HN