3 ms·

Thank you for being one of the few projects replacing a POSIX tool which properly sets the expectation that it's for personal use. It causes me no end of const

Thank you for being one of the few projects replacing a POSIX tool which properly sets the expectation that it's for personal use. It causes me no end of consternation that I see many tools introduced which provide only the barest minimum of functionality and skip over extended attributes, ACLs, and fail to keep compatibility with flags, or don't properly separate STDOUT & STDERR. While these may be sufficient for a naive developer, this oversight then breaks many downstream tools. Again though, thanks for sharing. Bringing your own spin and ideas into the world can be anxiety inducing and I'm pleased you went about this in a helpful and measured way!

concerndc1tizen 2y ago
Would you mind listing more common mistakes made by CLI developers?
- telgareith 2y ago
  These days: not building this such that they can be easily spit out as json and/or xml markup.
- two_handfuls 2y ago
  Not obeying the --help flag.
- fragmede 2y ago
  not behaving the same as robust cli tools. -h and --help and -v and --verbose and --version
- ksenzee 2y ago
  Julia Evans had an interesting thread recently on “social rules” of the terminal: https://social.jvns.ca/@b0rk/113540676612640547 https://social.jvns.ca/@b0rk/113540676612640547
- sphars 2y ago
  This is a good, open-source resource for guidelines on creating CLIs, which goes over some common mistakes. https://clig.dev/ https://clig.dev/
matheusmoreira 2y ago
If this is causing you any "consternation" at all, it means you expect too much from unpaid free software developers. The repository doesn't even have a sponsor link. The software is provided as is, in the hope it will be useful, but without any warranty whatsoever. All free and open source software licenses contain some version of the above statement. All of this is implicitly for personal use. In the sense that it's not a product, just something people made because they needed a problem solved.
- BrouteMinou 2y ago
  [flagged]
  - Koshkin 2y ago
    Indeed. Free shit is still... shit.
    - matheusmoreira 2y ago
      It's "shit" to you. To its creators, it's an awesome piece of software that does exactly what they wanted it to do and is as simple as they wanted it to be. They liked it enough that they thought it was worth sharing here. Maybe they don't need or care about extended attributes, and that's fine. If you want people to work on things they don't care about, you should consider hiring them or sponsoring their work. Either way, remember to thank them for their generosity. They did give you the source code and the freedom to use and modify it, after all. Copyright law says people are entitled to neither. If you won't pay them to get them to work on the features you want, it's entirely within your power to do it yourself. That freedom is not the default, it is a privilege that is given. People should be thankful for it. Even if the code sucked, you have the freedom to read it and learn from its mistakes and see what it does so you can make a better version. And the world is richer and wealthier because of it.
      - BrouteMinou 2y ago
        I totally see you adopting a sick dog/cat with all that extra emotions you have. Save a puppy! You can even brag on the social networks for some virtue signalling and karma points as bonus.

concerndc1tizen 2y ago

Would you mind listing more common mistakes made by CLI developers?

telgareith 2y ago
These days: not building this such that they can be easily spit out as json and/or xml markup.
two_handfuls 2y ago
Not obeying the --help flag.
fragmede 2y ago
not behaving the same as robust cli tools. -h and --help and -v and --verbose and --version
ksenzee 2y ago
Julia Evans had an interesting thread recently on “social rules” of the terminal: https://social.jvns.ca/@b0rk/113540676612640547 https://social.jvns.ca/@b0rk/113540676612640547
sphars 2y ago
This is a good, open-source resource for guidelines on creating CLIs, which goes over some common mistakes. https://clig.dev/ https://clig.dev/

matheusmoreira 2y ago

If this is causing you any "consternation" at all, it means you expect too much from unpaid free software developers. The repository doesn't even have a sponsor link. The software is provided as is, in the hope it will be useful, but without any warranty whatsoever. All free and open source software licenses contain some version of the above statement. All of this is implicitly for personal use. In the sense that it's not a product, just something people made because they needed a problem solved.

BrouteMinou 2y ago
[flagged]
- Koshkin 2y ago
  Indeed. Free shit is still... shit.
  - matheusmoreira 2y ago
    It's "shit" to you. To its creators, it's an awesome piece of software that does exactly what they wanted it to do and is as simple as they wanted it to be. They liked it enough that they thought it was worth sharing here. Maybe they don't need or care about extended attributes, and that's fine. If you want people to work on things they don't care about, you should consider hiring them or sponsoring their work. Either way, remember to thank them for their generosity. They did give you the source code and the freedom to use and modify it, after all. Copyright law says people are entitled to neither. If you won't pay them to get them to work on the features you want, it's entirely within your power to do it yourself. That freedom is not the default, it is a privilege that is given. People should be thankful for it. Even if the code sucked, you have the freedom to read it and learn from its mistakes and see what it does so you can make a better version. And the world is richer and wealthier because of it.
    - BrouteMinou 2y ago
      I totally see you adopting a sick dog/cat with all that extra emotions you have. Save a puppy! You can even brag on the social networks for some virtue signalling and karma points as bonus.