Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mac CLI – OS X command line tools for developers

github.com

Post reply on HN
Print view View original

31–40 of 75 posts

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

#31

Post by nicerobot »

compassios wrote: post #12
shykes wrote: 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.

Call it `morc`.

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

#32

Post by compassios »

shykes wrote: post #29
rahkiin wrote: post #25

Earlier quoted context omitted.

I do love 'Docker' though.

I do too, but I didn't choose it :) It was an internal codename picked by one of the early engineers on the project. In fact I firmly intended to change the name before launch - but we accidentally launched ahead of schedule and people loved it. The rest is history. A good example of my ineptitude at identifying good names.

That is why asking is always a good idea. I've met entrepreneurs that have the mindset that everything has to be an idea of themselves. I think that ego is a big player on their mindset.

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.

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

#33

Post by compassios »

nestlequ1k wrote: post #28
compassios wrote: post #12

Earlier quoted context omitted.

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

As an open source library, don't worry about it. If Apple causes a big stink about it (unlikely), then you can rename it. What you have is a great, simple, direct name for a utility script. Better to ignore the trademark / brand FUD.

I think that the name is not a problem but it's great to receive suggestions since a good idea could be suggested by someone from the community. Thanks for your comment!

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

#34

Post by compassios »

nestlequ1k wrote: post #27
JustSomeNobody wrote: post #26

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.

Exactly. In addition to that, this is a chance to collaborate to build more and better commands. It's the first step to what could be a powerful and very useful developer tool.

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

#35

Post by JustSomeNobody »

compassios wrote: post #34
nestlequ1k wrote: post #27

Earlier quoted context omitted.

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

Exactly. In addition to that, this is a chance to collaborate to build more and better commands. It's the first step to what could be a powerful and very useful developer tool.

There's already been collaboration among the various *nix operating systems.

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

#36

Post by JustSomeNobody »

nestlequ1k wrote: post #27
JustSomeNobody wrote: post #26

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.

man .

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

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

#37

Post by tacone »

compassios wrote: post #12
shykes wrote: 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.

Call it PC, and nobody will complain.

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

#38

Post by wtallis »

JustSomeNobody wrote: post #36
nestlequ1k wrote: post #27

Earlier quoted context omitted.

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

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.

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

#39

Post by emmelaich »

shykes wrote: post #20
compassios wrote: post #16

Earlier quoted context omitted.

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

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.

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

#40

Post by jwilcoxson »

wtallis wrote: post #38
JustSomeNobody wrote: post #36

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 this just layering the discoverability issue? It's another set of commands to learn, when you should be learning the real commands.
Post reply on HN