nowfound

Alternatives

Products that do what Jlq – A CLI to easily tail+query JSON log files using Rust+SQLite does

Hi all! It's been a while since I posted something. Wrote this back in November to scratch an itch regarding tailing logs locally for multiple services. I know we all love jq...but I'm quite comfortable with SQLite and SQL so just wanted to use that instead. Published my first Rust crate today! My first public Rust project so be gentle :) . Hope you enjoy it! https://crates.io/crates/jlq https://github.com/hamin/jlq

  1. 1GA

    Hi everyone! I’m excited to open source GritQL, a Rust CLI for searching and transforming source code. GritQL comes from my experiences with conducting large scale refactors and migrations. Usually, I would start exploring a codebase with grep. This is easy to start with, but most migrations end up accumulating additional requirements like ensuring the right packages are imported and excluding cases which don’t have a viable migration path. Eventually, to build a complex migration, I usually ended up having to write a full codemod program with a tool like jscodeshift. This comes with its own…

    2024 · github.com

  2. 2JI
  3. 3JQ

    I'm working on a tool that will probably involve querying JSON documents and I'm asking myself how to expose that functionality to my users. I like the power of `jq` and the fact that LLMs are proficient at it, but I find it right out impossible to come up with the right `jq` incantations myself. Has anyone here been in a similar situation? Which tool / language did you end up exposing to your users?

    Oct 2025 · jsonquerylang.org

  4. 4JA
  5. 5JE
  6. 6SP

    I love Jekyll, especially the Datafiles[0] feature, which lets you use CSV/JSON/YAML files and iterate through them. Mixed with the Jekyll Data Pages generator[1], which lets you create a page for every row in your dataset, it is a very powerful combination. However, Liquid is a terrible language for data-mangling, and simple filtering/sorting/merging can become very annoying. So I wrote a Jekyll SQLite plugin that lets you use the same data interface in Jekyll/Liquid, but backed by a SQLite file(s). It gives you the simplicity of the Baked Data pattern[2], and the…

    2024 · github.com

  7. 7TQ
  8. 8JA
  9. 9IB
  10. 10JA
  11. 11SS

    SPyQL (https://github.com/dcmoura/spyql) is SQL with Python in the middle, an open-source project fully written in Python for making command-line data processing more intuitive, readable and powerful. Try mixing in the same pot: a SQL SELECT for providing the structure, Python expressions for defining transformations and conditions, the essence of awk as a data-processing language, and the JSON handling capabilities of jq. How does a SPyQL query looks like? $ spyql “ IMPORT pendulum AS p SELECT (p.now() - p.from_timestamp(purchase_ts)).in_days() AS days_ago, sum_agg(price…

    2022 · github.com

  12. 12GL

    Hi HN. I've gotten pretty tired of needing to learn a custom programming language for a tool I use once a week or less. So I figured, it might be easier to pick up if `jq` used a programming language I already know. Voila, gq.

    2022 · github.com

  13. 13WJ

    Hey HN! Jaiqu is an AI agent for creating repeatable JSON transforms using jq query language syntax. Jaiqu translates complex JSON structures into repeatable jq queries. jq is a command line utility built for fast, reliable JSON queries. Jaiqu takes advantage of the LLMs for both constructing jq queries as well as using feedback to fix errors/invalid results if those queries are incorrect. Writing code to parse JSON is super annoying. It usually involves manually reading huge JSON balls, parsing the keys in a language of your choice, and pulling the data manually. Also, you're likely to…

    2024 · github.com

  14. 14LO

    I don't like the existing query languages for Elasticsearch and Grafana Loki, because they are too awkward to use for typical logs' investigation cases. So I designed new query language - LogsQL - and wrote reference implementation for it as a part of VictoriaLogs - an open source database for logs. LogsQL is based on the following principles: - Simplicity. It is easy to write typical queries over logs in it. For example, a single word `error` is a valid LogsQL query, which returns all the logs with the `error` word. Another example is `_time:5m error`, which returns all the logs with the…

    2024 · docs.victoriametrics.com

  15. 15MA
  16. 16JF
  17. 17AT
  18. 18QL

    qq is jq inspired interoperable config format transcoder with interactive querying. It features an optional interactive editor with autocomplete for structured data. And supports inputs and outputs for json, xml, ini, toml, yaml, hcl, tf, and csv to varying degrees of capability.

    2024 · github.com

  19. 19

    In-browser SQL Workbench for data querying & visualization

    2024

  20. 20PU

    2024 · github.com

  21. 21PA

    I built a Rust-based CLI/terminal UI for inspecting Parquet files—data, metadata, and row-group-level structure—right from the terminal. If someone sent me a Parquet file, I used to open DuckDB or Polars just to see what was inside. Now I can do it with one command. Repo: https://github.com/kaushiksrini/parqeye

    Nov 2025 · github.com

  22. 22JJ

    Hi all, I've made a javascript library to simplify searching/sorting/filtering in arrays of objects. Its inspired by both GraphQL and SQL, but implemented using javascript Proxies. Instead of creating a new language, its all just javascript. I've made it as part of an experimental database, which uses javascript as the query engine. The normal javascript map/reduce/sort functions are quite difficult to master for junior developers. JAQT is easier to explain, and can still be used in combination with any existing array functions. Please let me know what you think of the…

    2024 · github.com

  23. 23AE
  24. 24HA

    Hi all, we recently open sourced the first version of Hashquery, a Python library which lets you model analytics, DRY up common logic, and execute it against a database or warehouse. We were originally rendering SQL directly for all our queries, but that spiraled out of control with more complex analysis; the SQL needed to be changed sporadically for each new database dialect (BigQuery, Redshift, Aethena, Postgres, etc etc) and the SQL fragments were very challenging to reuse (and so fragments were copy-pasted all over). ~~~ Advantages we think it has over writing SQL by hand: - Queries are…

    2024 · hashquery.dev

Ranked by how close each launch is in meaning, then by votes. Refine with a description →