structured-ripgrep

Dev tools

code search

SHOW HN2023

15points
2comments
#1,931of 3,109 in 2023
Top 63%of 2023 by points

How HN took it

QuietFewer than 5 comments about the project

0 positive, 0 neutral or asking, 0 mixed, 2 critical, out of 2 comments about the project.

Execution: 0 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

  • Does not really use ripgrep's approach; parses every JSON line into memory then applies regex

    From 1 comment
    • While this is cool I don't see the relation to ripgrep. Ripgrep is about searching very quickly and extracting fixed strings to quickly skip over data. Looking at the JSON format…
      kevincox on HN
  • Name implies close relation to ripgrep without shared authorship

    From 1 comment
    • While I think it's great to explicitly cite ripgrep as an inspiration, and even to allude to it in the executable name, it doesn't feel right to me to call this…
      pxc on HN

Requests

  • Extract patterns for a prefilter search before parsing JSON

    From 1 comment
    • While this is cool I don't see the relation to ripgrep. Ripgrep is about searching very quickly and extracting fixed strings to quickly skip over data. Looking at the JSON format…
      kevincox on HN

Alternatives named

  • ripgrep

    From 2 comments
    • While this is cool I don't see the relation to ripgrep. Ripgrep is about searching very quickly and extracting fixed strings to quickly skip over data. Looking at the JSON format…
      kevincox on HN
    • While I think it's great to explicitly cite ripgrep as an inspiration, and even to allude to it in the executable name, it doesn't feel right to me to call this…
      pxc on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/35101237)