Why the name?
wiki.debian.org
Why the name?
1–10 of 101 posts
Re: Why the name?
#2> bc > originally a front-end for dc ("desk-calculator"); modern GNU bc is instead a backwards-compatible byte-code interpreter for dc, but what it stands for is still "basic calculator"
Re: Why the name?
#3Re: Why the name?
#4Re: Why the name?
#5Some pretty interesting explanations in this list. I personally prefer to not let the developers name things, because they usually come up with very bad names (hard to pronounce, hard to google for, have overtly sexual connotations, etc). Command line utilities are a little different because there's a culture of having short names making them easier to type. But it's still very hard to google for things like "less" b…
Re: Why the name?
#6Some pretty interesting explanations in this list. I personally prefer to not let the developers name things, because they usually come up with very bad names (hard to pronounce, hard to google for, have overtly sexual connotations, etc). Command line utilities are a little different because there's a culture of having short names making them easier to type. But it's still very hard to google for things like "less" b…
1. Naming things 2. Cache invalidation 3. Off-by-one errors.
Re: Why the name?
#7I had no idea! Makes me love it even more.
Re: Why the name?
#8Some pretty interesting explanations in this list. I personally prefer to not let the developers name things, because they usually come up with very bad names (hard to pronounce, hard to google for, have overtly sexual connotations, etc). Command line utilities are a little different because there's a culture of having short names making them easier to type. But it's still very hard to google for things like "less" b…
Searches for "Unix less" or "Linux less" are spot on. Even "less command line" will get you there easily. It's all about context. And of course there are always the man pages, which is usually the best place to start.
Re: Why the name?
#9Earlier quoted context omitted.
Searches for "Unix less" or "Linux less" are spot on. Even "less command line" will get you there easily. It's all about context. And of course there are always the man pages, which is usually the best place to start.
I personally find the man pages very dense and poorly organized. `man grep` for example is my own personal nightmare. I think the man pages should introduce a policy of simple usage examples instead of throwing 99% of information you don't care about at you at once. Something like http://bropages.org/