That's a fair question... ultimately it's possible to get something similar using other tools, but IMO it won't be as easy. Just as a contrived example with a simple query:
The problem I really wanted to solve for myself was primarily discovery for standard interfaces. I don't write Go code as regularly as I'd like and don't have code review from a professional setting.
I regularly forget where/whether interfaces and constants exist, so I made myself this ranked & filterable search tool.
The hosted deployment covers the standard library + a few other packages, but it's built to be able to be pointed at any (internal) codebase too! Just need to build an index with more packages installed https://github.com/g-harel/gothrough
I had a similar problem diffing large API responses a few months ago and implemented an automation friendly JSON schema tool. It's a great way to make a summary of the data, especially when looking for forgotten fields for example.
NPM needs to make accessing the source code easier. It has always bothered me that the linked repository can be set to absolutely anything the author wants.
I think something like an npm diff command would be helpful. This would allow you to see the changes from a previous version that you just upgraded from. This would somewhat replicate the functionality that commiting your node_modules directory to git would give you.
Not sure how that would help. Anyone can publish anything to npm, it doesn't even need a repository. So unless the source code itself was hosted on npm, and the entire toolchain was controlled by npm, there's not much to do.
Not sure how much it could add to the conversation, but I implemented a library to find almost minimal superpermutations in go a while back. Uses a technique I didn't see anywhere else.
This method produces superpermutations of length 1! + 2! + ... + n!, which was believed for a long time to be the best possible. But Greg Egan’s new result shows it’s possible to do a lot better than that.
https://gothrough.dev/search?q=writer
https://github.com/search?q=repo%3Agolang%2Fgo+writer&type=c...
The problem I really wanted to solve for myself was primarily discovery for standard interfaces. I don't write Go code as regularly as I'd like and don't have code review from a professional setting.