4 ms·

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 yo

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.

compassios 10y ago
If you have any suggestion regarding the name, just let me know! I am open to receive suggestions about that. Thanks!
- vonklaus 10y ago
  I think you should name it Mac CLI. If you really think it is an issue just call it MaCLI.
  - shykes 10y ago
    What about "macly"? :)
  - givinguflac 10y ago
    I was going to suggest the same name.
    - compassios 10y ago
      And that is definetely a good suggestion! Thanks
shykes 10y ago
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?

compassios 10y ago

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

vonklaus 10y ago
I think you should name it Mac CLI. If you really think it is an issue just call it MaCLI.
- shykes 10y ago
  What about "macly"? :)
- givinguflac 10y ago
  I was going to suggest the same name.
  - compassios 10y ago
    And that is definetely a good suggestion! Thanks

shykes 10y ago

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?