upvote

points

by plastic0419 hours ago |
comments
upvoteby cedws8 hours ago|
next
[-]
GitHub stars have been botted to hell for a long time now. I don't know how the farms acquire so many accounts, last time I tried to register a GitHub account I had to jump through so many hoops. The platform needs an overhaul, starting with requiring a valid payment method for the social features.
reply
upvoteby 0x694208 hours ago|
prev|
next
[-]
victor's legit and people have been excited about his work for years; squashing the history was just a bit of an optics oopsie on his part. the star to fork ratio makes perfect sense for something like bend.

- fstar: 3k stars, 267 forks

- coalton: 1.8k stars, 111 forks

- carp: 6k stars, 267 forks

- c3: 5.8k stars, 400 forks

when something is novel/young (not having had time to grow large and accumulate issues in the vein of "1 doc page out of 1000 is worded incorrectly") and (as of yet) niche (innate barrier to entry for contribution because you have to learn from square 1 what all the moving parts look like), you don't see the same activity patterns on public source hosts as with a general-purpose language.

reply
upvoteby plastic0418 hours ago|
parent|
[-]
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.

reply
upvoteby LightMachine8 hours ago|
parent|
next
[-]
The 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!
reply
upvoteby LightMachine6 hours ago|
parent|
[-]
commit history is back now!
reply
upvoteby 0x694208 hours ago|
parent|
prev|
next
[-]
victor 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.
reply
upvoteby debo_7 hours ago|
parent|
prev|
[-]
This obsession over GitHub stars is quite bizarre.
reply
upvoteby LightMachine8 hours ago|
prev|
next
[-]
I honestly had no idea people would be so upset about commit history. I just wanted to avoid leaking sensitive info, that's all. I'm running through the commits to ensure nothing personal leaks and I plan on putting the history back.

Also Bend's stars came on the V1 launch. This is V2. It already had 20k before.

reply
upvoteby plastic0418 hours ago|
parent|
[-]
> Also Bend's stars came on the V1 launch. This is V2. It already had 20k before.

This is the reason you should not reomve your commit history. How would anyone know that there were V1, and it was already popular?

If you need to remove sensitive data, you should use tools like git-filter-repo.

- https://docs.github.com/en/authentication/keeping-your-accou...

- https://github.com/newren/git-filter-repo

reply
upvoteby LightMachine7 hours ago|
parent|
[-]
Commit history is back!
reply
upvoteby 8 hours ago|
prev|
[-]
deleted
reply