[baq]

looks nothing like jq

  1. let $stats := collection("stats")
  2. for $access in $stats
  3. group by $url := $access.url
  4. return 
  5. {
  6.   "url": $url,
  7.   "avg": avg($access.response_time),
  8.   "hits": count($access)
  9. }

[keymone]

> besides the syntax

[mro_name]

isn't that question like "cinema besides the movies"?

[chii]

the user experience. jq is often a one liner, terse and expressive. This jsoniq language looks almost like a scripting language, requiring multiple lines to write an expression.

[_wolfie_]

I have multiple 30+ lines jq scripts in my current project. So "often a one liner" is true, but it is not a requirement, so I'm still not sure why use this instead.

[keymone]

no, language is not just syntax.

[mro_name]

Nor is the cinema just movies.

[keymone]

so if cinema isn't just movies then what's the problem with asking about the difference in "cinema besides the movies"?

[mro_name]

it's senseless besides nit-picking.

[jbverschoor]

> JSONiq borrows a large numbers of ideas from XQuery

So basically grep or even sql ->xquery. No thank you!