2 ms·
About forks alone I get it, but look at their issues. - fstar: 2K issues, stars-issue ratio: 0.6. - coalton: 700 issues, ratio: 0.4 - carp: 450 issues, ratio
by plastic041 17d ago
About forks alone I get it, but look at their issues.
- fstar: 2K issues, stars-issue ratio: 0.6.
- coalton: 700 issues, ratio: 0.4
- carp: 450 issues, ratio: 0.08
- c3: 1.9K issues. ratio: 0.3
Bend has 300 issues for 20K stars so ratio is about 0.02. Maybe their followers starred the repo as a fan activity? It could explain too many stars and too few forks/issues/prs.
- LightMachine 17d agoThe project got a lot of attention at launch, but it wasn't really ready to be used back then. There were too many limitations, like u24 numbers (yes), 2 GB memory limit, pervasive strictness (if-then-else executed both branches). It was just not practical.I think (hope) that explains a lot of it. But honestly there is also my own failure into making the language actually be used, rather than just a viral moment :( I hope it will be different this time!
- LightMachine 17d agocommit history is back now!
- 0x69420 17d agovictor has courted a very llm-enjoyer audience and such people are famously prone to hype (which is kinda brutal in its own way cause the language itself is cool and i dont wanna make it sound like im taking away from that). but yeah, fan activity as you put it easily accounts for the missing order of magnitude, if you like.
- debo_ 17d agoThis obsession over GitHub stars is quite bizarre.
- nullbio 17d agoWhen the original bend released in 2024 it was mega-hyped, but then interest died off fairly quickly, hence the stars + lack of issues. Now they're re-using the same repo to release the new version.