Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Jless, a command-line JSON viewer

pauljuliusmartinez.github.io

Post reply on HN
Print view View original

71–80 of 91 posts

Re: Show HN: Jless, a command-line JSON viewer

#71

Post by _ikke_ »

tenken wrote: post #60
1vuio0pswjnm7 wrote: post #57

Humble request: musl version Keeping a glibc chroot directory takes up a fair bit of space, leaving less space available for other stuff. Whenever I try compiling Rust programs it exhausts the available space I have. Hence I am resorting to begging, starting now (because this program sounds potentially very useful.) Please folks, if possible, include musl versions in addition to glibc. :)

It's 2022 and you're running out of disk space?

Yes, the same reason that programs remain slow, even though computers keep getting faster.

Re: Show HN: Jless, a command-line JSON viewer

#72

Post by sshine »

dan-robertson wrote: post #15

This looks great. So far the only tools I have are: function jql() { jq -C "$@" | less -R ; } and an abuse of the preview feature in fzf room let you interactively write a jq query.

I do exactly this, and I’m very happy with it. I tried switching to another tool like Jless when it got posted on HN last year, but it wasn’t enough of a game-changer compared to jq itself.

I don’t get to interactively change the query, but hitting ‘q’ and running another jq query is in some sense more powerful, because it does not just allow me to “focus the lens” but also completely alter it.

Building a jq query by progressively testing and viewing is really nice. I love jq!

Re: Show HN: Jless, a command-line JSON viewer

#73

Post by stavros »

danso wrote: post #9

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!

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.

Re: Show HN: Jless, a command-line JSON viewer

#74

Post by afarrell »

westoncb wrote: post #52
pferde wrote: post #25

I'm loving it, and certainly will be using it a lot. One thing, though - 2MB seems like a lot for program of this kind. In comparison, jq on my system has 30kB.

I'll bet there are some Rust build options they can tweak to get it way down...

I'll bet that a good project for a different person who has idly thought "y'know, I'd like an excuse to learn rust..." could be doing that.

Re: Show HN: Jless, a command-line JSON viewer

#75

Post by e12e »

stavros wrote: post #73
danso wrote: post #9

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!

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.

Clearly there should be integration tests/automation that outputs asciinema examples?

Re: Show HN: Jless, a command-line JSON viewer

#76

Post by stavros »

e12e wrote: post #75
stavros wrote: post #73

Earlier quoted context omitted.

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.

Clearly there should be integration tests/automation that outputs asciinema examples?

How do you mean? Is a log not basically the same?

Re: Show HN: Jless, a command-line JSON viewer

#77

Post by e12e »

stavros wrote: post #76
e12e wrote: post #75

Earlier quoted context omitted.

Clearly there should be integration tests/automation that outputs asciinema examples?

How do you mean? Is a log not basically the same?

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?

Re: Show HN: Jless, a command-line JSON viewer

#78

Post by stavros »

e12e wrote: post #77
stavros wrote: post #76

Earlier quoted context omitted.

How do you mean? Is a log not basically the same?

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 do…

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.

Re: Show HN: Jless, a command-line JSON viewer

#80

Post by peakaboo »

_ikke_ wrote: post #71
tenken wrote: post #60

Earlier quoted context omitted.

It's 2022 and you're running out of disk space?

Yes, the same reason that programs remain slow, even though computers keep getting faster.

I don't think that's the reason... It's because so called modern stacks are built on 100 layers of abstractions instead of being low level and fast.
Post reply on HN