Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Quite apart from the fact that many (most?) vim short forms have long form equivalents, and vim has autocomplete - this argument feels misguided to me, mostly because I don't see why it would be limited to just vim. It seems natural, if you hold such a position, to also advocate abandoning CLIs like `ls`, `cd`, `jq`, `aws`, et al? - and I would despise having to put up with stuff like:

    $ change-directory foo/bar
    $ amazon-web-services elastic-compute-cloud describe-instances
    $ javascript-object-notation-query ...
Not to mention short parameters: `ls -AF`, `grep -v`, `curl -H`, ...

One of my most valuable resources is time. I would rather invest it in learning each tool's vocabulary than spend so much time typing (a prefix longer than the existing name, tab, then pick the answer) in an "everything is spelt out in full, acronyms and abbreviations are banned" world.



Looks just like Powershell.


which interestingly enough can also have things abbreviated, ie Invoke-Web-Request can be used as iwr.


Yes, but they all have shorthand aliases.

When writing a script or documenting you use the long form, when using a shell you use short form.


Welcome to the cargo cult hell that descriptively named all the things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: