The growth of command-line options, 1979-Present

Re:The growth of command-line options, 1979-Present by rb808 on Tuesday March 03, 2020 @09:12AM (#22474548)

I think its just a reflection of how much more widely software is used, how complicated our environments are, how many admins/developers there are compared to the old days. Eg the aws command is hugely complicated, but I'm not sure breaking it out into smaller commands easily really would make anything easier, just pollute the command line namespace.

[ Parent | on HN ]

Re:The growth of command-line options, 1979-Present by lotwxyz on Tuesday March 03, 2020 @10:40AM (#22475325)

In my web-based shell implementation [0], I use a library concept, such that you have to "import" commands into the current execution environment. You can either do this kind of thing:

  $ import fs

This imports all the commands in the 'fs' library, without any concern for namespaces, and if there are any already existing commands with the same name, they are not overwritten (the new ones are not imported).

But if you do this:

  $ import fs as myfs

Then, all the commands in the 'fs' library are invoked like this:

  $ myfs.vim

[0] https://dev.lotw.xyz/shell.os

[ Parent | on HN ]

Re:The growth of command-line options, 1979-Present by mjcohen on Tuesday March 03, 2020 @07:33PM (#22480161)

Are you notified of the ones that are not imported?

[ Parent | on HN ]