13 ms·
Mac CLI – OS X command line tools for developers
- Etheryte 10y agoAs 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.
- compassios 10y agoThanks for your comment. I will be updating the code to add modularity in addition of improvements to make it easier to use and extend.
- andruby 10y agoThat would be great! I would love to have some mac specific commands, but I don't care for the lamp/magento/git commands. Is there a way to install only the dependencies that one cares about?
- mmfZ4e4OqQ7RRwP 10y agoNot 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.
- eridius 10y agoLooks like a nice collection of tools, but unfortunately the installation process assumes you want to install Homebrew (as if you haven't already), install pip, and install git, pv, and python through Homebrew. I don't want to perform those steps. I already have Homebrew, pip, and git installed, and I have pv and python installed using Nix.
- compassios 10y agoThat's true. One of the pending tasks on the script is modularity in addition of a customizable installation process. Stay tuned!
- pskocik 10y agoI'm quite unfond of this command suite pattern that seems to be popular in cli apps lately. It's a very git thing to do. Why not just mac-whatever1 mac-whatever2? It has less coupling, basic autocompletion out of the box, and generic autocompletion very easily generatable in a context-free fashion, but less coupling alone should be enough of a reason.
- compassios 10y agoI agree 100% with you. I am working on a modular version of the script and I will update the code soon. Thanks for your comment!
- pskocik 10y agoI appreciate your appreciating my jibe. Good luck with your suite and sorry for the little bit of negativity. Command line apps are my favorite type of apps.
- compassios 10y agoNo problem! I am glad that you enjoy command line apps as much as I do. Sometimes negativity brings energy to change what needs to be changed. If you see that you have ideas to contribute to the project, I look forward to your contributions!
- deleted 10y ago[deleted]
- shykes 10y agoI 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.
- compassios 10y agoThanks for your advice! Do you have any suggestion regarding the name? I'd love to hear some ideas.
- shykes 10y agoI 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.
- compassios 10y agoThanks for advice, and if you think of anything about the name just let me know!
- JustSomeNobody 10y agoWhat's so wrong with the regular command line commands for most of this?
- nestlequ1k 10y agoMost people don't memorize the commands for all of these, and googling for them everytime gets old.
- compassios 10y agoExactly. 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.
- JustSomeNobody 10y agoThere's already been collaboration among the various *nix operating systems.
- JustSomeNobody 10y agoman <command>. And if people are in the command line often enough, they do memorize the actual commands. They really, really do.
- wtallis 10y agoman pages don't really solve the discoverability problem.
- jwilcoxson 10y agoIsn't this just layering the discoverability issue? It's another set of commands to learn, when you should be learning the real commands.
- mymosh 10y ago
- gradstudent 10y agoThis project rather reminds me of Joel Spolsky's Law of Leaky Abstractions: http://www.joelonsoftware.com/articles/LeakyAbstractions.html http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
- vbezhenar 10y agoI 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.
- compassios 10y agoThat is great! Could you create a Github Issue to move forward with that?
- rafa2000 10y agoHow about 'climate'?
- ohthehugemanate 10y agoHa - I just got it. CLImate, right? I like it. I was gonna suggest something like termtool, or just term.
- datihein 10y agoPlease, everyone, stop forcing HomeBrew as a dependency. HomeBrew screws with your systems file permissions and installs directly into the standard system directories. MacPorts (https://www.macports.org/ https://www.macports.org/) is at least a good, and it installs into the /opt tree, staying out of the way of anything Apple or Darwin wants to do when updating or patching your system. Don't like MacPorts? There's always Fink (http://www.finkproject.org/ http://www.finkproject.org/), which installs into /sw and looks like Debian (i.e. apt-get). HomeBrew seems like the worst of the three. :-(
- glasz 10y agoi've been using homebrew since, like, lion and never had major issues. it also always worked across major and minor mac os upgrades. the things it does in /usr/local don't interfere with mac os. in contrast, i somehow couldn't manage to efficiently use macports and fink.
- jimjag 10y agoI really don't get this... it seems like simply a way to create an environment where you need to prepend 'mac' to every command.
- juandazapata 10y agoWhy?