100k

8 ms·

31.
by 100k 3y ago
If this interests you, I recommend The History of English podcast. The episodes on Old English cover similar linguistic evolution that happened due the influence of Old Norse. https://historyofenglishpodcast.com/
32.
by 100k 3y ago
Wikipedia: "After passing 9,000 metres (30,000 ft), one of the outer Plexiglas window panes cracked, shaking the entire vessel." If anyone else is curious about why the cracked window didn't cause an implosion, I found the an
33.
by 100k 3y ago
SpaceX deliberately decided not to use a flame diverter for that launch site, which is a few hundred feet from an endangered bird nesting area. It's clear they could have done more to avoid damage to nearby wildlife and property and it
34.
by 100k 3y ago
Absolutely. There are regular darkroom classes you can sign up for. It's kind of hard to get a spot because the classes are small but my teacher said people also have learned how on YouTube and then come in to practice.
35.
by 100k 3y ago
San Francisco has the Harvey Milk Photo Center, which has a huge dark room and film processing facilities. It's pretty awesome. I've taken several classes there. https://www.harveymilkphotocenter.org/
36.
by 100k 3y ago
Amazing, hearing it played sends chills down my spine. It's not as old, but in Wernor Herzog's documentary "Cave of Forgotten Dreams", an archeologist plays a 30,000 year old vulture bone flute. It even uses the pentaton
37.
by 100k 3y ago
We want to do it right if we do implement it, but I can't promise anything concretely. It's not trivial, unfortunately.
38.
by 100k 3y ago
Thanks for your patience! It has been a long road with some dead ends (we've wanted to add this since 2012 at least). We actually wrote about why we didn't just use grep in our last blog post: https://github.blog/2
39.
by 100k 3y ago
(I work on code search.) Yeah, sorry about that. We've heard this feedback a lot. There's two reasons why we haven't implemented this. First, content is shared between repositories which makes this harder than before, when it
40.
by 100k 3y ago
Since Lucene already supports ANN vector search, I am curious how this project is different than what's in core.
41.
by 100k 4y ago
I read this novel and didn't really care for it much. I thought the idea of completing massive projects with the fractional attention of tens of thousands of people was hard to take. Coordination costs and context switching are a large
42.
by 100k 4y ago
Hi, I work on GitHub code search. Grep.app is based on Solr and indexes about 500,000 public repositories. As far as I know, the author has not shared their tokenization strategy, but based on the the results I expect they are indexing trig
43.
by 100k 4y ago
(I edited this post.) Maybe that could have been worded more clearly... What we mean is repositories with atypical activity patterns, for example a busy monorepo with lots of files and continuous pushes. If we sharded by repository, a singl
44.
by 100k 4y ago
Yes. You can also use regular expressions to limit your search. Details: https://docs.github.com/en/search-github/github-code-search/...
45.
by 100k 4y ago
How do you think Algolia shards their data given that architecture? My guess is that Algolia's indices are sharded by customer and each cluster probably has multiple customer indices. do you keep a copy of the index document form of
46.
by 100k 4y ago
Sorry, there are size limits on the number of files in a repositories that we'll index. That is probably why your repository wasn't indexed. Out of curiosity, what are you storing in this repository?
47.
by 100k 4y ago
(I work on this.) If you check out our prior blog post, "A brief history of code search at GitHub" ( https://github.blog/2021-12-15-a-brief-history-of-code-searc... ), you can learn a bit about the evolution of this
48.
by 100k 4y ago
Thanks! I enjoyed reading your blog posts about building your code search engine. One minor point of clarification, we do not use a positional ngram index, which as you note blows up the index size. Instead, we use the covering sparse ngram
49.
by 100k 4y ago
I agree! Search is so cool. It's interesting that GitHub seems to have quite a few shards. Algolia basically has a monolithic architecture with 3 different hosts I used to work at an Algolia competitor. I don't know for sure, bu
50.
by 100k 4y ago
We hope to share more on this soon!
51.
by 100k 4y ago
You are correct, as I mentioned, we do not analyze symbols for C and C++ at this time.
52.
by 100k 4y ago
Have you tried the new search? Thanks to the variable length ngram indexing mentioned in the post, it can handle all of those cases. Sign up here to try it: https://github.com/features/code-search Symbol extraction for
53.
by 100k 4y ago
You can try it right now in our beta. Right now, we are onboarding all signups daily. Sign up here: https://github.com/features/code-search Obvious disclaimer because I work on this (and I also worked on the legacy sea
54.
by 100k 4y ago
Thanks for the feedback! That's coming, we've been prioritizing scaling the index and ingest process and haven't had a chance got add that yet. There are a bunch of value-add features like this I am looking forward to knockin
55.
by 100k 4y ago
I also upgraded to a split keyboard and I love it. I really liked the Microsoft Natural keyboard, but slamming my mouse into the number pad was driving me crazy, so I decided to get a split keyboard without one. I have the Kinesis Freestyle
56.
by 100k 4y ago
At a general audience level, "Index" is on my list to read. It covers the invention of the index up to digital search engines. https://www.nytimes.com/2022/02/09/books/review-index-histor... &q
57.
by 100k 4y ago
(I worked on the backend for this, not the frontend.) Yes, the new code search and navigation experience is powered by React for the frontend. We decided to use that because we wanted to build a stateful, rich navigation experience. If you
58.
by 100k 4y ago
Yes, Stack Graphs power code navigation for supported languages (currently, Python). We also use tree-sitter parsers for CTags-style symbol navigation.
59.
by 100k 4y ago
This is addressed in the FAQ. It will be included with GitHub, just like the current code search.
60.
by 100k 4y ago
No, it is a custom-built search engine for code. grep.app is great, though.

More ›