|
|
|
|
|
by tuxlifan
1585 days ago
|
|
I have no idea about the odds and didn't bother to look up the timeline but I can give you some anecdata and tell you exactly why I might have theoretically been the 4th lurker-become-excited-commenter for this post, were I to read this first on the computer instead of on my phone (and nearer real time than on a following weekend) and less hesitant to post comments in general: I find json to be a PITA to parse as a human when looking at getting a bigger picture or keys/values that are strewn away from each other and not just e.g. two values next to each other. Anytime I have to do something with it, I have to search through my history to dig out some jq invocation and then try to tweak it correctly to do what the (most of the time similar but also different enough) task at hand needs. My mind sadly just seems to be unable to sufficiently grok jq. So when I read here about jless I was stoked and the excitement was strong enough to want to dig out my login credentials and make a comment along the lines of "This is AWESOME! Thank you so much for making life easier!". In the end, when I logged in on the computer and had reflected more, I opted to upvote a comment instead and then saw this thread; so thank you, I guess, for providing me an opportunity or excuse to express my enthusiasm in addition to that. I consider my discovery of jless
(which sadly I was apparently not able to make on my own while searching the internet for json tools previously - so yay for lurking on HN :-) - but it might also partly be the relative (to my predicament) youth of the tool)
of similar importance to me as macros in vim or back in the days using bluefish for editing HTML as they all save my time being spent on doing tooling to do things and instead allow it to being spent on doing things directly. (BTW thanks to all these devs!) Just my 2 cents :-)
(and I'm not particularly interested in starting or partaking in any further discussion) |
|