|
|
|
Ask HN: We got 100 stars. A weekend project got 12k. What are we missing?
|
|
2 points
by lilwing
78 days ago
|
|
This week Graphify launched off the back of a Karpathy tweet. 48 hours to build and 1k stars. in 2 days. It uses an llm to INFER system structure literally labeling its own edges as "inferred" we launched Ix a week ago. its an open source CLI that maps any codebase into a persistent architectural graph so ai agents stop relearning your system every session.
100 stars in 10 days. Graphify got 12k in 48 hours. when a tool is built in 48 hours anf outpaces months of engineering in star velocity is that a signal about the product itself or the timing?? does the better technical approach win eventually or is the early momentum most important. I think we have the better solution but also aware i might just be wrong about what the market wants right now. can anyone look through our repo and tell us? would be super helpful.ill put the link in comments |
|
In my case I went with graphify because I am using OpenCode, and it seemed plausible that Sonnet would at least have gotten that part right about Graphify having better support for OpenCode. Now that I take a second look though, I realize there is a plugin for adding Ix into OpenCode (https://github.com/ix-infrastructure/ix-opencode-plugin) so now I'm contemplating migrating to Ix - the hooks available in that plugin appear to be better than what I have now with Graphify. I really dislike that graphify hooks rebuild the graph post-commit, since I want to include the graph files in my git repo.