| ▲ | skywhopper 2 hours ago | |||||||
Not every use case of jq is a person using it interactively in their terminal, believe it or not. | ||||||||
| ▲ | mikkupikku 2 hours ago | parent | next [-] | |||||||
If somebody needs performance, they probably shouldn't be calling out to a separate process for json of all things, no? (Honestly, who even still writes shell scripts? Have a coding agent write the thing in a real scripting language at least, they aren't phased by the boilerplate of constructing pipelines with python or whatever. I haven't written a shell script in over a year now.) | ||||||||
| ||||||||
| ▲ | 7bit an hour ago | parent | prev [-] | |||||||
If Ms performance is a main concern, you shouldn't use jq. Believe it or not. | ||||||||