I'm kind of an outlier when it comes to development, but I really hate using OSX. One thing that makes it bearable for me (I have a mac at work), however, is that I can get exactly what I want with very little hastle using homebrew. I would like to add to this sentiment, on this turkey day, homebrew has my thanks.
Usability feels like a second hand citizen to me, when it comes to things like window management / snapping. I come from a very windows-heavy background, so I appreciate the shell experience provided by OSX, but really hate the ear-flicks of trying to use multiple apps simultaneously, and snapping between them, positioning them, etc, in an OSX world.
To be fair, this could be a training / learn-ability issue that may not be present had I learned OSX first.
This really is the easiest thing to fix in macOS, just install magnet (in the app store). I does window snapping in all the places, with shortcuts too.
Hell, I remember using Linux 15 years ago and having better space management than I have in MacOS today. I honestly hate how they nerfed spaces and made it much harder to work with many applications, or on many projects.
Just give me project contexts, dammit!
Windows is just as bad, if not worse these days though.
The other day I went into iTerm2, changed to the top of my Xcode projects top directory and did "find . | xargs grep abcd". Nothing was found. This wasted my time for 30 minutes and then I did a cd to the directory where the Swift files were and did the same command. Immediately I saw the file with the abcd string in it.
This type of thing doesn't happen to me on Ubuntu.
That said, things like iTerm2, Homebrew etc. do make using MacOS somewhat tolerable.
Your Xcode project directory probably had spaces in its path somewhere (which, for reasons of rather outdated conventions, is less common to encounter under Linux.)
Like with any other Unix, dealing with spaces in the arguments passing through a pipeline to xargs(1) requires the NUL-delimited style:
find . -print0 | xargs -0 grep abcd
or you can stop worrying about the spaces by letting find(1) handle them:
find . -exec grep abcd \{\} \;
or, even better, get grep(1) to do the whole job (which also has the advantage of tagging each found line with the filename the result was found in):
Seconding homebrew being the one of the few things that makes using OS X bearable. Pqrs also gets my turkey day thanks for making Karabiner, which is another one of those things.
Why install git from Homebrew? Git is included in macOS. Sometimes the Apple version of a program is outdated or just different but macOS Sierra has git version 2.13.6, less than six months old.
Installing it from homebrew requires minimal effort and can keep you more up-to-date than the system version. It requires more effort to figure out that the included version is "only" half a year old than to just install a newer version from homebrew.
21 comments
[ 4.7 ms ] story [ 67.0 ms ] threadK thanx Bye. Back to snarfing all the data. Especially cool since homebrew has homebrew usage analytics, we love to consume that data!
Reading formulas of other software is useful too.
To be fair, this could be a training / learn-ability issue that may not be present had I learned OSX first.
Hell, I remember using Linux 15 years ago and having better space management than I have in MacOS today. I honestly hate how they nerfed spaces and made it much harder to work with many applications, or on many projects.
Just give me project contexts, dammit!
Windows is just as bad, if not worse these days though.
The other day I went into iTerm2, changed to the top of my Xcode projects top directory and did "find . | xargs grep abcd". Nothing was found. This wasted my time for 30 minutes and then I did a cd to the directory where the Swift files were and did the same command. Immediately I saw the file with the abcd string in it.
This type of thing doesn't happen to me on Ubuntu.
That said, things like iTerm2, Homebrew etc. do make using MacOS somewhat tolerable.
Like with any other Unix, dealing with spaces in the arguments passing through a pipeline to xargs(1) requires the NUL-delimited style:
or you can stop worrying about the spaces by letting find(1) handle them: or, even better, get grep(1) to do the whole job (which also has the advantage of tagging each found line with the filename the result was found in):I started to use the standard terminal and found it much more responsive that iTerm2. I never used most of the iTerm2 features anyway.
I'm sticking to the standard terminal for the time being.
[1] https://brew.sh/analytics/