4 ms·

Glad I fought the reflex to jump straight into the comments with "So how is this different than jq" and instead actually clicked through to see the wonderful ho

by danso 5y ago

Glad I fought the reflex to jump straight into the comments with "So how is this different than jq" and instead actually clicked through to see the wonderful homepage that instantly answered my question via animated GIF. I'm a sucker for trying out any new CLI tool and this looks genuinely and immediately useful. Thanks!

graderjs 5y ago
Excellent! The expected future value of the comment thread thanks you for that sterling effort. It was a pretty wonderful homepage right? I don't have any need for it now whatsoever, but this project looks like a useful debugging tool if you need to reverse engineer undocumented APIs. And the author's write up is comprehensive informative and well written. And their site looks good so this is an awesome Show HN I think.
- pdimitar 5y ago
  That's one of the most informative and compact pages about a tool that I've ever seen. Compliments to whoever made it!
stavros 5y ago
It's so good, it's convinced me to add asciinema recordings to more of my utilities. The only problem is that they tend to get stale.
- e12e 5y ago
  Clearly there should be integration tests/automation that outputs asciinema examples?
  - stavros 5y ago
    How do you mean? Is a log not basically the same?
    - e12e 5y ago
      I mean that if asciinema examples in the readme tends to get outdated (ed2: "stale") , they should be kept up to date via CI and (probably) be part of the integration tests; if a commit changes the ux/interaction tests should reflect that, and documentation should be easily (automatically) updated? Ed: like if you for a web app have selenium/browser tests that somehow also takes screenshots that become part of the documentation?
      - stavros 5y ago
        Ah, I see. That's probably a bit too much tooling for a small OSS utility, manual updates would get me a long way there. The other issue is that it doesn't matter that the UI is exactly up to date, just good enough to give the user an idea of the functionality.
        ZeroGravitas 5y ago
        It's a generally good idea though, website screenshots (and thinking about it now, animations) from test automation is another similar task. Not quite standard practice, though some people do bits of it here and there, but both probably should become so which would amortize the cost over lots of cli tools.

by danso 5y ago

graderjs 5y ago

Excellent! The expected future value of the comment thread thanks you for that sterling effort. It was a pretty wonderful homepage right? I don't have any need for it now whatsoever, but this project looks like a useful debugging tool if you need to reverse engineer undocumented APIs. And the author's write up is comprehensive informative and well written. And their site looks good so this is an awesome Show HN I think.

pdimitar 5y ago
That's one of the most informative and compact pages about a tool that I've ever seen. Compliments to whoever made it!

stavros 5y ago

It's so good, it's convinced me to add asciinema recordings to more of my utilities. The only problem is that they tend to get stale.

e12e 5y ago
Clearly there should be integration tests/automation that outputs asciinema examples?
- stavros 5y ago
  How do you mean? Is a log not basically the same?
  - e12e 5y ago
    I mean that if asciinema examples in the readme tends to get outdated (ed2: "stale") , they should be kept up to date via CI and (probably) be part of the integration tests; if a commit changes the ux/interaction tests should reflect that, and documentation should be easily (automatically) updated? Ed: like if you for a web app have selenium/browser tests that somehow also takes screenshots that become part of the documentation?
    - stavros 5y ago
      Ah, I see. That's probably a bit too much tooling for a small OSS utility, manual updates would get me a long way there. The other issue is that it doesn't matter that the UI is exactly up to date, just good enough to give the user an idea of the functionality.
      - ZeroGravitas 5y ago
        It's a generally good idea though, website screenshots (and thinking about it now, animations) from test automation is another similar task. Not quite standard practice, though some people do bits of it here and there, but both probably should become so which would amortize the cost over lots of cli tools.