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.
Mac CLI – OS X command line tools for developers
11–20 of 75 posts
Re: Mac CLI – OS X command line tools for developers
#12I 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.
Re: Mac CLI – OS X command line tools for developers
#13As a seasoned dev on OS X I'm not sure if I see the benefits here. You get the same set of instructions but lose (or rather, don't gain, as a beginner) the chance to use google-fu.
Not only that, by abstracting cross platform commands for things like git you give up the knowledge which allows you to go to other platforms and work there. Unless this mac thing would be ported to linux, windows, etc.
Re: Mac CLI – OS X command line tools for developers
#14I 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.
i think the difference is that this is an open source command line utility for mac, so the naming convention is essentially mac command line utility. I think you are correct that it could cause issues, but nowhere near the same thing as Commodo wherein they intentionally are trying to undermine a competitors offering by intimidation and coercion.
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.
Re: Mac CLI – OS X command line tools for developers
#15I 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.
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.
Re: Mac CLI – OS X command line tools for developers
#16Earlier quoted context omitted.
Thanks for your advice! Do you have any suggestion regarding the name? I'd love to hear some ideas.
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!
Re: Mac CLI – OS X command line tools for developers
#17I 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.
i think the difference is that this is an open source command line utility for mac, so the naming convention is essentially mac command line utility. I think you are correct that it could cause issues, but nowhere near the same thing as Commodo wherein they intentionally are trying to undermine a competitors offering by intimidation and coercion. Not sure what a better name would be, but it may need to be changed. I…
If you have any suggestion regarding the name, just let me know! I am open to receive suggestions about that. Thanks!
Re: Mac CLI – OS X command line tools for developers
#18I 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.
i think the difference is that this is an open source command line utility for mac, so the naming convention is essentially mac command line utility. I think you are correct that it could cause issues, but nowhere near the same thing as Commodo wherein they intentionally are trying to undermine a competitors offering by intimidation and coercion. Not sure what a better name would be, but it may need to be changed. I…
I agree the circumstances are very different, and obviously don't think there was any nefarious intentions. But the underlying fundamental issue - brand recognition and the value of having your work recognized under a name you control - is still the same.
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?
Re: Mac CLI – OS X command line tools for developers
#19Earlier 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!
I just thought of CLImax. Might be to sexually loaded though :(
Re: Mac CLI – OS X command line tools for developers
#20Earlier 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!
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 let armchair quarterbacks like me demotivate you :)