Me too. Sometimes one informs or inspires the other, but so far it seems that is about it.
264 karma · joined April 3, 2012
Me too. Sometimes one informs or inspires the other, but so far it seems that is about it.
No. They are turning coding into a monopolistic monoculture. Not everybody loves pull request-based workflows, you know.
Do people still buy into this? I feel this phrase was just a marketing ploy by GitHub.
The maintainers of packages are supposed to port their software to the relevant platform, that's their job, and yes sometimes this takes some work, whereas Homebrew seems to assume that ./configure; make; make install should flawlessly work out of the box for pretty much anything (this is not true). The fact that they actively discourage even trying to install outside of /usr/local is simply laziness (and not in a good way). This is a foolish and naive approach, and pursuing this idealistic, reductive approach for "simplicitly" breaks down very, very quickly. MacPorts is a well behaved, self-contained system, and a well designed one at that. Homebrew just dumps everything into a system directory that it really shouldn't have exclusive rights to in the first place (/usr/local).
Moreover, there is nothing wrong with installing extra compilers, libraries, etc, under /opt/local and having them run alongside the system libraries. Lots of systems have provisions for doing something like this.
Also, using version control systems as distribution and deployment systems is a horrible anti-pattern and I really, really wish people would stop doing this.
Homebrew's documentation is terrible. Its terminology is facile and stupid in the way it analogizes everything with beer.
> Perhaps Paul Davis could apply, and claim to be Pauline Davis for internship purposes.
How utterly reactionary.
Moreover, do you realize just how despicably transphobic or queerphobic this statement is? The irony in your comment is appalling. Your comment is a perfect example of precisely why we do need to support people who don't conform to heteronormative stereotypes.
It's concise and readable. Every word is used for a reason.
Not everybody loves this book, you know. A lot of people find its sloppy, disorganized, chatty style quite irritating.
> Not sure the highly theoretical stuff is actually worth anything as far as getting things done, unless you go on to study Algebra and mathematics in general.
You've answered your own question. It's "highly theoretical", not "highly practical". The focus is different by definition.
This is a common thing to say, but it's untrue. A cheap and nasty instrument will have bad features that are noticeable even to beginners. Things like poor quality finishing, hardware that rattles, sharp edges on the edge of the fretboard where the frets haven't been smoothed off properly, etc, etc, and it's really uninspiring if your guitar isn't enjoyable to hold. Even more "advanced" things like having the right action or a comfortable neck radius are noticeable early on. Tuning heads are another big one, cheap tuning heads are awful (the difference between good and bad ones is like night and day), and if your guitar is constantly going out of tune due to that or something else, and if you're not completely tone deaf, you will notice and it will annoy you.
How did you get this impression? It has little basis in reality.
Yes. This should be the very core of the argument, with a focus on the words "conseqeunces" and "incentive".
Has anything as good been released since? What is the current "standard reference" on DNS and BIND?
Me too. He often asks for corrections in light of these types of oversights (at least, it looks like an oversight to me).
Uh, I'm not so sure about this. Programmers tend to have a bad habit of severely overestimating their own intelligence. This is one of the things I dislike about the profession: Everybody is so self-assured of their own brilliance.