Live data from Hacker News

HomeBrew Analytics – top 1000 packages installed over last year

brew.sh

151–160 of 168 posts

Re: HomeBrew Analytics – top 1000 packages installed over last year

#151

Earlier quoted context omitted.

The popularity of ripgrep, ag, ack, etc., is an object lesson in "defaults matter." I don't say this in the prescriptive sense, i.e., "hey, you, you should care about defaults!", but rather, in the descriptive sense, i.e., "there are a lot of people out there that care about the defaults." The second lesson to learn is that people care about the difference between "results are instant" and "there is a bit of noticeab…

Have you considered problem of printing searched results to terminal? I saw it is detailed little bit in your blog, but one of the things that bothers me is - say I am searchin for string "foo" in a 2GB log file. There are usual number of matches, nothing unusual. But typically, I am not really looking for string "foo". I guess most users who are grepping log files are also looking for strings/text that appear slight…

I use -C 20 combined with a pager.

rg foo -C 20 -p | less -R

Also, yuck, that command line. Glad I have those hidden behind shell scripts.

Re: HomeBrew Analytics – top 1000 packages installed over last year

#152

Earlier quoted context omitted.

The popularity of ripgrep, ag, ack, etc., is an object lesson in "defaults matter." I don't say this in the prescriptive sense, i.e., "hey, you, you should care about defaults!", but rather, in the descriptive sense, i.e., "there are a lot of people out there that care about the defaults." The second lesson to learn is that people care about the difference between "results are instant" and "there is a bit of noticeab…

Have you considered problem of printing searched results to terminal? I saw it is detailed little bit in your blog, but one of the things that bothers me is - say I am searchin for string "foo" in a 2GB log file. There are usual number of matches, nothing unusual. But typically, I am not really looking for string "foo". I guess most users who are grepping log files are also looking for strings/text that appear slight…

Thoughts have crossed my mind, but it's a wickedly hard problem. My personal opinion is that once you start trying to solve the problem you're describing, then you really start to venture away from "line oriented searcher" to "code aware searcher" in a way that invites a lot of trade offs. The most important trade off is probably maintenance or complexity of the code.

In particular, in order to better show results, I kind of feel like the search tool needs to know something about what it's showing. Right? How else do you intelligently pick the context window for each search result? For code, maybe it's the surrounding function, for example.

The grep -C crutch (which is also available in ripgrep) is kind of the best I've got for the moment for a strictly line oriented searcher. `git grep` has some interesting bits in it that will actually try to look for the enclosing the function and emit that as context. I think it's the `-p/--show-function` flag. ... But that doesn't really help with your log files.

In any case, I am very interested in this path and even have an issue on the ripgrep tracker for it: https://github.com/BurntSushi/ripgrep/issues/95 --- I'm not sure if it really belongs in ripgrep proper, but I would really love to collect user stories. If you have any, that would be great. Examples of what you'd like the search results to look like would be great!

Re: HomeBrew Analytics – top 1000 packages installed over last year

#153

Earlier quoted context omitted.

Have you considered problem of printing searched results to terminal? I saw it is detailed little bit in your blog, but one of the things that bothers me is - say I am searchin for string "foo" in a 2GB log file. There are usual number of matches, nothing unusual. But typically, I am not really looking for string "foo". I guess most users who are grepping log files are also looking for strings/text that appear slight…

I use -C 20 combined with a pager. rg foo -C 20 -p | less -R Also, yuck, that command line. Glad I have those hidden behind shell scripts.

Hehe, yeah, I have `rgp` in my $HOME/bin:

    #!/bin/sh
    
    exec rg -p "$@" | less -RFX

Re: HomeBrew Analytics – top 1000 packages installed over last year

#154

Earlier quoted context omitted.

I use -C 20 combined with a pager. rg foo -C 20 -p | less -R Also, yuck, that command line. Glad I have those hidden behind shell scripts.

Hehe, yeah, I have `rgp` in my $HOME/bin: #!/bin/sh exec rg -p "$@" | less -RFX

[deleted]

Re: HomeBrew Analytics – top 1000 packages installed over last year

#156
post #48

Earlier quoted context omitted.

Debian publishes statistics gathered by the optional "popularity-contest" package at http://popcon.debian.org I can't remember whether the default is opt-out or in with the current installer.

It prompts if you want to install it. It also doesn't sent data to a privacy abusing company like google.

> It also doesn't sent data to a privacy abusing company like google.

Actually the data is sent to Google.

Re: HomeBrew Analytics – top 1000 packages installed over last year

#157

Earlier quoted context omitted.

> How often do you handle files large enough to observe a difference between grep, ack, ag and rg ? > I'm willing to bet that most people, even in the subset who use grep "a lot" (defining "a lot"...), wouldn't see a significant improvement. Daily, but not for the reasons that I think you're thinking. I work in Python a lot, which means there is typically a virtualenv in the tree somewhere, sometimes more than one. T…

Possibly redundant information, but still: ag has those same features. I see lots of reasons to choose rg/ag over grep, but none yet to choose rg over ag.

I intended to mention in my original post, but I appear to have forgot: I'm only comparing rg/grep; I have no experience with ag, so I can't speak to it. rg was my first "better than grep" tool, and it's filled my needs quite well. (Enough so that I've not felt the need to investigate ag.)

Re: HomeBrew Analytics – top 1000 packages installed over last year

#158

autojump should be higher. It's insanely handy once it gets your directories indexed.

I have been using z[1] for a _long_ while now, lovely little thing [1] https://github.com/rupa/z

Seconded, it's a great utility, without dependencies, and very simple.

Re: HomeBrew Analytics – top 1000 packages installed over last year

#159

Earlier quoted context omitted.

> At least then it can be fixed, instead of seeing the "No formula found" text. You don't see that text but instead text indicating the formula has been deleted. > The culture of deletion surrounding the long tail of digital artifacts just doesn't make any sense. They will be preserved in the Git history for as long as we continue to use Git. Both the above comments make it seem like you've not really done any resear…

The best defense is a good offense. I express concern about your project's use of Google Analytics and then releasing that data to the public, then about the culture of deletion; and I am criticized for my "lack of research". Sorry I touched a nerve; but all of these issues are decisions that are being made, to not expect critiques of your decisions is naive. Anyways. Having done my research: > You don't see that tex…

Well I happen to agree with your sentiments. I've been meaning to make a fork of homebrew that doesn't have these problems. You should checkout out tigerbrew.

Re: HomeBrew Analytics – top 1000 packages installed over last year

#160
Don't know what half of these are? Here's some quick and dirty Javascript to make each formula clickable to a detail page:

    document.querySelectorAll("td > code").forEach(code => code.innerHTML = `${code.innerText}`)
Cut and paste that in your Javascript Console (`View/Developer/Javascript Console` on Chrome) when you're on https://brew.sh/analytics/install-on-request/.
Post reply on HN