4 ms·
The one major thing I really like about the terseness of these commands is that, although they have a steeper learning curve at first, once you learn them --- w
by userbinator 8y ago
The one major thing I really like about the terseness of these commands is that, although they have a steeper learning curve at first, once you learn them --- which happens quickly with repeated use --- they feel very natural and you use them almost as if they're an extension of English, like a special dialect; talking with coworkers, we use words like "cat", "grep", "ls", "sudo", etc. as verbs.
Contrast this with the verbosity of more "modern" command languages like Powershell: while those may be a bit easier to understand the very first time, every time thereafter it feels like you're talking in a language where every word is a minimum of 10 letters and two syllables long. The mental overhead is far higher.
I've always remembered "bss" as the "bull-shit segment" --- because it initially doesn't have any useful content.
- chimprich 8y agoThe commands you list aren't too bad because they get quickly learned through use. And "grep" at least is pronounceable and feels strangely apt as a command name. In general though I think the terseness of the standard Unix commands is a problem, particularly for less often used commands. Even after many years of using them I still get "du" and "df" confused, for example.
- dkersten 8y agoI always end up using both du and df because I can never remember which does what. Half the time, I also can’t remember their names even and have to look them up. All of the really frequent commands, I can remember (cp, mv, cat, tar, head, tail, ls, mkdir, rm, grep, sed, and a handful of common programs like package managers and git) and everything else I can never remember and have to look up. I personally don’t like the unix command names, most don’t make much sense to me personally. Sure, I like that they’re short, but I can never remember them unless I use them a lot.
- nomocrypto 8y agoDon’t worry, I’m exactly the same way. disk fills up Me: Dammit, which command is which again? angry Googling It’s like the syntax for creating a symlink: I could live to be 100 and still forget the order of the arguments to ln.
- KozmoNau7 8y agoI always remember them as "disk usage" and "disk free".
- netsharc 8y agoBut how.. du = disk usage, df = disk free...
- chimprich 8y ago"Disk usage" could plausibly be the command that tells you how much space you've got left. Maybe "disk free" doesn't apply quite as well to du's function. If I was designing them from scratch, I'd maybe call them something like "size" and "space" respectively.
- JackCh 8y ago> "Disk usage" could plausibly be the command that tells you how much space you've got left. "Red touches yellow, you're an okay fellow. Red touches black, you're a dead jack" It's a good thing there aren't any coral snakes around where I live.
- userbinator 8y agoThe way I remember du and df is Disk Usage and Display (mounted) Filesystems, respectively.
- technofiend 8y agoI learned Unix in the mid 80s but it wasn't until sometime later I learned or had the epiphany that grep was shorthand for g/re/p. As in global search for regular expression and print the results. Talk about a forehead slapping moment. Not everything in Unix is immediately obvious.
- stephengillie 8y agoTab completion to the rescue! Once you're a few letters past the dash in Powershell, you can just hot the tab key until you've cycled through the few commands it spells. Same for parameters.
- _ikke_ 8y agoDoesn't help that a lot of commands have the same prefix 'Get-' / 'Set-', 'Add-', etc, so you have to type at least 6 characters, including a '-', to get useful completion.
- stephengillie 8y agoThese are the approved verbs. Powershell function names have to be in "verb-noun" format, forcing a level of standardization on the language. It seems like an odd idea to me. https://msdn.microsoft.com/en-us/library/ms714428(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/ms714428(v=vs.85).a...
- jazzdev 8y agoPowershell has aliases, so you can use 'ls' instead of 'Get-ChildItem'. My colleagues tend to use Get-ChildItem in scripts and ls when typing at the command prompt. Personally, I prefer 'ls' for scripts too. I would never use "rd" for a variable name, but since I speak Unix, the more concise 'ls' seems better. To my colleagues without a Unix background, Get-ChildItem, probably is a better choice.