←back to thread

Mozilla Firefox – Official GitHub repo

(github.com)
848 points thefilmore | 9 comments | 13 May 25 05:23 UTC | HN request time: 1.259s | source | bottom
Show context
bandrami ◴[13 May 25 06:03 UTC] No.43969975[source]▶
Pretty cool that Linus Torvalds invented a completely distributed version control system and 20 years later we all use it to store our code in a single place.
replies(29): >>43969999 #>>43970002 #>>43970008 #>>43970018 #>>43970019 #>>43970028 #>>43970031 #>>43970032 #>>43970036 #>>43970037 #>>43970142 #>>43970154 #>>43970198 #>>43970282 #>>43970314 #>>43970343 #>>43970418 #>>43970419 #>>43970431 #>>43970434 #>>43970451 #>>43970472 #>>43970541 #>>43970904 #>>43971268 #>>43971299 #>>43971387 #>>43971586 #>>43988717 #
IshKebab ◴[13 May 25 06:08 UTC] No.43970002[source]▶
Plenty of people use Codeberg and Gitlab. And it's still distributed - I don't need to lock files and ask coworkers if I can work on them.

Maybe if Git had native support for PRs and issues this wouldn't have happened. (And yes I'm aware of git send-email etc.)

replies(3): >>43970054 #>>43970113 #>>43970150 #
1. qwertox ◴[13 May 25 06:42 UTC] No.43970150[source]▶
In Codeberg, how does one even search for files containing a given string? Probably the #1 thing I do on GitHub is searching for files in a project containing a given string.
replies(3): >>43970190 #>>43970201 #>>43971145 #
2. sph ◴[13 May 25 06:49 UTC] No.43970190[source]▶
Given how terrible GitHub search in files is, what I usually do is clone the repo and run ripgrep.
replies(3): >>43970268 #>>43970391 #>>43970500 #
3. jimbob45 ◴[13 May 25 06:50 UTC] No.43970201[source]▶
That exact exercise filled a quarter of my workday today.
4. eXpl0it3r ◴[13 May 25 07:00 UTC] No.43970268[source]▶
Not sure when you tried last, but it's gotten a lot better over the years. If you need something from the latest master, you'll be able to find it.
5. nicce ◴[13 May 25 07:18 UTC] No.43970391[source]▶
If the repository is indexed, there isn’t really competitive search. You can find blog posts about it. They actually used ripgrep at some point. (not anymore I guess because too slow?).

Edit: ripgrep was just a test

More: https://github.blog/engineering/the-technology-behind-github...

6. mrweasel ◴[13 May 25 07:42 UTC] No.43970500[source]▶
But Github is actually pretty good at searching for something across all files in a repo.
replies(1): >>43971336 #
7. throwaway290 ◴[13 May 25 09:29 UTC] No.43971145[source]▶
I'm not being sarcastic but how do you do it on github?;) it basically never works

Not only results are incomplete but it seems once they went into training LLMs on all code they host they made sure no one else can do the same easily and so now everything is madly rate limited.

Every time I just clone and grep.

8. IshKebab ◴[13 May 25 10:05 UTC] No.43971336{3}[source]▶
Not remotely as good as grep.app.
replies(1): >>43977904 #
9. qwertox ◴[13 May 25 21:26 UTC] No.43977904{4}[source]▶
I was shocked at how fast I was able to find "Open an audio file and read as mono waveform, resampling as necessary" of whisperX in audio.py on grep.app.

It was instantaneous. But where do I go from there? I cannot navigate through the code. It shows me where I can find that string, but that's it. I also cannot look at blame to see when that line got edited.

Though thanks a lot for bringing this onto my radar.