4 ms·
My comment was too negative. Looks very useful. I just have trouble remembering names like this. I don't think this is a name/sound that clicks for me.
by rileymat2 8y ago
My comment was too negative. Looks very useful. I just have trouble remembering names like this.
I don't think this is a name/sound that clicks for me.
- agumonkey 8y agoI get the feeling too. I was just wondering about that this morning. Some times you want a name that is clearly descriptive like lock_and_clean_journal but when you have a new tool that does a lot and in a different way.. a cute name is a good symbol to indicate 'completely new context'. Otherwise we'd get meaningless glue code like pony | lulee --pew | eels | cyan ..
- masklinn 8y ago> Otherwise we'd get meaningless glue code like > pony | lulee --pew | eels | cyan .. I mean we kinda do, it's just that we're used to the bits. ls | xargs cat | grep main >> /dev/nul 2>&1 is not inherently more meaningful than what you wrote above, you just have the experience to interpret it. Incidentally, powershell commands tend to be more "self-explanatory" in their naming, at least in theory.
- agumonkey 8y agoheh, not untrue, although most are bad shortenings.. ls:list, xargs:arguments, cat:concatenate MS did try to avoid explosion of idioms but at a tiny verbosity cost. I believe that map/reduce is a bit a good middle ground