j
Languages and libraries
json parser
SHOW HN2015
13points
5comments
#1,715of 2,565 in 2015
Top 67%of 2015 by points
How HN took it
QuietFewer than 5 comments about the project
1 positive, 0 neutral or asking, 0 mixed, 2 critical, out of 3 comments about the project.
Docs: 1 for, 1 againstIdea: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
Objections
Not practically useful compared to jq.
From 1 comment
Its an interesting idea but what does this achieve that jq [1] doesn't already do, and likely faster? [1] http://stedolan.github.io/jq/
stephenr on HN
Source is 94 lines, not 20 as claimed.
From 1 comment
Looking at the source[1] it stands at 94 lines. There's also no example of field extraction in the readme even though it's mentioned that there is an example below in the…
anonfunction on HN
README lacked a field extraction example.
From 1 comment
Looking at the source[1] it stands at 94 lines. There's also no example of field extraction in the readme even though it's mentioned that there is an example below in the…
anonfunction on HN
Questions
What does this achieve that jq does not already do?
From 1 comment
Its an interesting idea but what does this achieve that jq [1] doesn't already do, and likely faster? [1] http://stedolan.github.io/jq/
stephenr on HN
Alternatives named
jq
From 1 comment
Its an interesting idea but what does this achieve that jq [1] doesn't already do, and likely faster? [1] http://stedolan.github.io/jq/
stephenr on HN