Hacker News new | past | comments | ask | show | jobs | submit | 100k's comments login

As someone who was against the Iraq war, it's hard to express how important Paul Krugman's columns were to me at the time. It felt like the world had gone mad, but he provided an island of sanity. And he was right about the war.

I also appreciate Krugman's rediscovery of current music as an older person. It encouraged me to keep exploring.

My favorite Krugman moment is him visiting the White House after he won the Nobel Prize. This photo of him with Bush (who he'd been railing on for 8 solid years) is priceless: https://freakonomics.com/2008/11/bush-congratulates-krugman/


Zeke Faux's Number Go Up (https://www.amazon.com/Number-Go-Up-Cryptos-Staggering/dp/05...) started as an investigation into Tether. He found some extremely suspect clues, but he wasn't able to crack it. Hopefully the feds are able to shed some light on it.


It's quite fun, I played a lot of it during the pandemic. It's sort of like Advance Wars, but when you lose you can choose to send one of your leveled up characters back in time, which lets you use them again in a new game.


Yes, you can use CGO to call Rust functions using extern "C" FFI. I gave a talk about how we use it for GitHub code search at RustConf 2023 (https://www.youtube.com/watch?v=KYdlqhb267c) and afterwards I talked to some other folks (like 1Password) who are doing similar things.

It's not a lot of fun because moving types across the C interop boundary is tedious, but it is possible and allows code reuse.


There's some interesting companies in this space.

https://gofourth.com/ - focusing on grid storage, uses graphite (carbon) and liquid tin for heat transfer

https://antoraenergy.com/ - industrial heat and electricity

https://rondo.com/ - industrial heat

You can find interviews with their founders on the Volts podcast.


I’m happy to see Standard Ebooks here! I’ve read their editions of Nostromo by Joseph Conrad and Vanity Fair by William Thackeray and the quality great. I recommend it if you’re interested in classic literature.


Yes. The concepts apply to all programming languages. The exercises use multiple programming languages. For example, one exercise has you explore the Git source code (which is in C) to learn how to use a program's data structures to understand an unfamiliar codebase. Other examples have you find bugs in Python code or write Java.


Tree-sitter is very cool! We use it to power semantic analysis for GitHub code search.


(I gave this talk and work on code search.)

Sorry you've had a frustrating experience with the product. When we look into complaints about missing results, it's almost always one of two things. First, the repository is not indexed yet, but searching triggers indexing. Future searches work. Second, the files or the repo hit our documented limitations (https://docs.github.com/en/search-github/github-code-search/...). I think these limits are pretty reasonable, but we need to do a better job making it clear why content isn't in the index.


> First, the repository is not indexed yet

I understand this is important. But the issue I have is that it’s hard or maybe impossible to know what’s been indexed and what isn’t.

I run a few orgs with hundreds of repos. Which are indexed? I don’t know.

This makes your search suck for my organization. I understand the reasons. They aren’t reasonable for me. I don’t want to search using your tool if it won’t work for my org.

Code search isn’t just for what’s popular. It needs to be for what is real and accurate.


Yeah, we need to do better on the visibility of this for owners. And we're trying to scale the system so it's not a problem at all. In the meanwhile, you can ask support to index all the repos in your orgs and we can take care of it.


When a user search includes a non-indexed repository, GitHub needs to include a warning message along with the search results, something similar to what you just mentioned:

"One or more repositories of this search is not yet indexed, please try your search later for accurate results."

Likewise for the 2nd case.


For the repositories not in the index, we do show a message to try again later. For documents that have been excluded, we agree we need better visibility.


Do you list the repos not in the index?


What does "Exhaustive search is not supported" mean? (that phrase is from your link, in the bullet-points near the top)


It means that we have a result limit. If a term matches in a lot of files, not all the hits will be shown.


I work on this, and I agree we should do more to improve ranking. Exact duplicates are supressed, but often forks have different versions of some files, so they come up in the results.

If you don't want to see forks, you can exclude them. Here's your same search, but converted to a regex and not including forks. I only get 3 results.

https://github.com/search?q=%2Fload%5C%28%22%40rules_foreign...


Not including forks should be the default IMO. There can be a button in the Advanced section of the sidebar to include them.


Are you at all embarrassed at all by how buggy and intentionally unusable Github has become?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: