Earlier quoted context omitted.
So you are saying it represents which technologies the community considers cool? Because that's exactly the context in which I'm quoting it :)
no I'm saying it isn't a good view into what people actually like. it's a view into what they want the world to be like. people respond to surveys according to what they want the survey results to be, and not how things actually are.
GitHub Star History Graph
61–70 of 79 posts
Re: GitHub Star History Graph
#62we are building a similar tool https://ossinsight.io/ which saves nearly 45B events from GitHub and can let you get more powerful insights from the project, e.g here is the history insights for K8s https://api.ossinsight.io/share/1bdadc17-6d94-41fb-8bc4-d6dc... , enjoy it by yourself :-)
Some feedback though, I found it really hard to understand what the cost would be for "Trying my own dataset" (After the first year) and how TiBD factors in and would be used. All obvious links for TiBD go direct to a signup page which I don't want to fill without some understanding/validation of the service I'm signing up for. Removing the path of this signup page, in an attempt to go to the root URL to learn more, then takes me to an Auth0 access page. I appreciate I may not be your target market, but just giving my view of someone thinking "This looks cool, how much would it cost to have a customized version of this?"
Re: GitHub Star History Graph
#63Just to share a trick, you can also use markdown to embed a live star history chart to your GitHub README. e.g.
## Star History
[![Star History Chart](https://api.star-history.com/svg?repos=bytebase/star-history...
Instruction: https://star-history.com/#bytebase/star-history&Date
Enjoy~
Re: GitHub Star History Graph
#64Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?
Before you incorporate someone's Github library into your own project, you want to know some things. Is it secure? Is it well-maintained? Is there an active userbase to help with support? Stars are one indicator of this.
Re: GitHub Star History Graph
#65Earlier quoted context omitted.
For every professional React developer, there's probably ten people who consider React cool and something to learn in the future, while they haven't even heard about Svelte or Vite.
Doubtful anyone thinks react is cool at this point. It’s more of a thing you just need to use for your job. It’s like Java at this point.
Re: GitHub Star History Graph
#66Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?
> Yet it seems to be a popularity contest people care about for some reason Before you incorporate someone's Github library into your own project, you want to know some things. Is it secure? Is it well-maintained? Is there an active userbase to help with support? Stars are one indicator of this.
Re: GitHub Star History Graph
#67If you want see the effect of HN on a new repository: https://star-history.com/#samwillis/tetra&Date It was on the HN homepage for about 5 hours yesterday, never higher than about 25. The initial jump on the 25th was some attention on Twitter. Also the HN link was to the website, not the GitHub. I imagine if it had been a link to the repository the stars would be higher.
Re: GitHub Star History Graph
#68Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?
> Yet it seems to be a popularity contest people care about for some reason Before you incorporate someone's Github library into your own project, you want to know some things. Is it secure? Is it well-maintained? Is there an active userbase to help with support? Stars are one indicator of this.
Re: GitHub Star History Graph
#69Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?
It makes me feel good when I see one of my projects getting stars. When I star a project it is with the hope that another maintainer will have a similar good feeling.
Re: GitHub Star History Graph
#70Slightly related, but... what is it with stars? I've never starred a repo and don't understand why I would want to. Yet it seems to be a popularity contest people care about for some reason, even though it correlates strongly with forks/issues/prs so you get the same idea about usage from those. Does it go at all beyond a "like", or am I just too old to get it?