71–75 of 75 posts
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`?
1) It's already muscle memory.
2) It's not hard.
3) Other *nix OSs use is too.
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`?
I see this as either being used frequently enough to be easily memorized, or infrequently enough that a quick check of the man page is fine. The real benefit is that it's a very general solution that works on basically any system, and for a wide variety of commands. As another commentor pointed out, the apropos command makes this strategy even more powerful.
Please, 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/ ) 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.f…
in contrast, i somehow couldn't manage to efficiently use macports and fink.
As 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.
Thanks for your comment. I will be updating the code to add modularity in addition of improvements to make it easier to use and extend.
Is there a way to install only the dependencies that one cares about?