Live data from Hacker News

How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

medium.freecodecamp.com

31–37 of 37 posts

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#31
post #8

Ignoring the fact that Github Stars are a aweful metric for anything else than vanity, "More bells and whistles" feels like a terrible advice and you should much more focus on a "easy-to-get-started" readme with just the minimal amount of beels and whistles to effectively communicate what your thing is really about.

I'm extatic one of my project reached 100 stars. Sometimes we need to feel good.

Agreed. I also think there's a lot of satisfaction in knowing that you got those stars in a completely organic manner.

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#32

Also their user onboarding literally forces a unknowing user to create a GitHub account then star their specific repository. Making GitHub stars ultimately meaningless, if they ever meaned anything.

I always assumed stars were just a form of bookmarking for me to find projects again easily, since there is no other method than 'watching', which results in too much info

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#33
post #2

Despite the title, the article raises an interesting point: why do we prefer new code, with less features, to old but robust projects. > Unfortunately, we were affected by cognitive bias: old code is bad code. But the truth can be the opposite. The old code is battle-tested by thousands of users in hundreds of different projects. Most of the critical bugs have been fixed, the documentation is complete, there are tons…

Old last commit date could mean two things: 1. Project left in unfinished state and development stalled, in which case it's reasonable to run away from it. 2. Project done (fulfilling it's purpose) and turned to maintenance mode, in which case I'd be quite happy (as a matter of fact I'd prefer) to use it as I know I'm dealing with a stable codebase and don't need to be afraid of breaking changes in the future. I thin…

I find that additionally (presuming github or similar) that looking through for any recent issues helps a lot... npm download rate is another metric for comparison. Thouse some obscure bits may not see so many downloads at all.

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#34

Also their user onboarding literally forces a unknowing user to create a GitHub account then star their specific repository. Making GitHub stars ultimately meaningless, if they ever meaned anything.

These guys really care about Github stars.

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#35

Hey, I'm the author of the "GraphQL Visualizer" tool ( http://nathanrandal.com/graphql-visualizer/ ) that they mention in the article as inspiration for their project. This new project is quite nice and definitely a step up from mine. Also wanted to mention that there is a CLI version of the visualizer at https://github.com/sheerun/graphqlviz for when you want to quickly visualize a GraphQL endpoint for documentation…

[deleted]

Re: How we got 1,500 GitHub stars by mixing time-tested technology with a fresh UI

#37
post #22
post #19

Earlier quoted context omitted.

http://githubstars.com this a really helpful site. curl project got 5k stars from it :p

I believe your parent comment censored censored the link to avoid boosting the site's page rank. You may want to edit your comment (or not).

confused. it is just a funny website.
Post reply on HN