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

51–60 of 75 posts

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

#51

Post by bossmanstan »

compassios wrote: post #44
emmelaich wrote: post #39

Earlier quoted context omitted.

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.

i'd just call it maCLI

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

#53

Post by retreatguru »

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.

What about max?

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

#56

Post by compassios »

pje wrote: post #52
JustSomeNobody wrote: post #26

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

Well, would you rather remember: `sudo shutdown -r now` or `mac shutdown`? Would you rather remember: `pmset sleepnow` or `mac restart`?

Exactly, that is the point. Also, some commands require several parameters and it's much better having the script asking for those parameters in an interactive way.

For example: mac ssh:download-folder

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

#57

Post by Waterluvian »

Razengan wrote: post #46
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.

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.

Without reading the article I assumed this would be some tutorial on official Mac OS tools. Once I read it, it was obviously not the case.

Just anecdotal evidence.

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

#58

Post by Razengan »

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.

You way want to change all occurrences of "OS X" to "macOS" :)

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

#59

Post by vbezhenar »

I would suggest another command. Instead of "XXX:extract" I use my little shell script, which runs correct unarchiver basing on the file name (or series of unarchivers for common cases like .tar.gz). So you don't have to memorise every command out there. Another useful functionality is to create a separate directory, if archive contains multiple "root" files, so the current directory won't be polluted by the bad archive.

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

#60

Post by dottedmag »

pje wrote: post #52
JustSomeNobody wrote: post #26

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

Well, would you rather remember: `sudo shutdown -r now` or `mac shutdown`? Would you rather remember: `pmset sleepnow` or `mac restart`?

Is there complementary `linux shutdown` and `freebsd shutdown` and `solaris shutdown`? If no, then this utility only increases cognitive load.
Post reply on HN