Trending tabs are being deprecated due to low usage
github.com
github.com
Weirdly, I've been low-key worried about it ever since they added the "Spoken Language" dropdown, which AFAICT is the only real change from the last few years.
It's not that I think being able to search by spoken language is bad or anything, it just screams of a middle manager trying to "solve" the important problem of a few people being confused about how the "language" filter referred to the programming language, and the solution was "let's add another button!"
The fact that this is the only filter they’ve added in years, and it is next to a different “language” drop-down doesn’t suggest that they’re really interested in making filtering actually helpful — but that they’re trying to solve one specific label being a source of confusion by adding another button.
A project of mine that tracks project mentions (in real time) on Hacker News and Reddit to determine trending repos.
Just a nitpick: I'd like to see the repo org or author in the repo listings. The top 20 is currently listing 3 different stable-diffusion repos with no obvious differences (except for the ranking scores).
The reason is that at some point a few years ago, the trending list was filled with Chinese repositories which makes it useless if you don’t speak the language. The language filter fixed it for me and made the page useful again.
Please don't do this - plenty of service auto-translate descriptions and they drive me crazy. If the description is in a language I don't speak then at least I know that I can skip it. But if it's auto-translated then I'll click on the repo, only then realize that I don't understand it, go back and try again with the next repo.
The only situation in which I would welcome such a change would be if GitHub translated comments, function names, variable names, READMEs and all documentation (including screenshots and reference guides not hosted on GitHub) AND THEN translated my contributions back from my language to the original one.
At some point I actually tried to read some of these projects and they often were complete garbage (empty repositories or disgusting code) or completely specific to China. The useful projects tended to have an English readme anyway.
This honestly made me realize there’s kind of a fracture in open source between China and the west: Chinese don’t speak English, and the west doesn’t speak Chinese. It’s almost like they have parallel libraries for everything we routinely use. Which makes sense because we rarely provide Chinese documentation on our projects.
This comes off as inflammatory. It sounds like you're misrepresenting GP's desire to filter out a language they cannot read as a kind of bigotry against the speakers of that language.
That may explain the apparent disapproval from the community.
As for auto-translation, there are plenty of browser extensions and other solutions if people want that.
I also do agree with the filter itself purely because I ran into the same problem too, lots of Chinese repositories with poor if any English READMEs.
For me, the Trending page is even more useful than Explore page. Still wondering why Explore page has more spotlight than Trending page.
When one of my (quite obscure) repos get stars, I feel joy. I like to think starring someone else's repo has that same reaction for them, too.
- Saying "I think it's neat" internet points is kindof a nice kudos. It's relatively pleasing to see some stars on your repositories.
- It's an indication of popularity/usage. If you have to rely on some dependency, "choose the one with the most stars" will probably give you a good result for next to no effort.
- In terms of social networking: I can then see what repositories others have starred.
The trending page otoh is nice and fresh, though I wish they'd change it to prevent already popular repos like typescript from "trending" (why are people starring this? ridiculous.)
I think this hints at part of the problem with Github as a social hub for tech. I do the same thing, and star things I've seen in the Trending page. Very often I never actually go back to those things though. That star is essentially a signal to the repo owner saying "I'm happy this exists." The problem is that there are also people who star things to say "I love this" or "I am using this" or simply "I'm bookmarking this."
That's fine, of course, but then repo owners then start saying things like "My library has 5000 stars, it's clearly the best library for X!" and "My library got to 20000 stars much more quickly than Y and Z, so people must think it's better than Y and Z!"
Github probably should turn off the social features unless they can think up a way of discouraging people using the social aspect as a measure of quality or popularity when they're really not those things.
By the way, you mean uninterested :)
From [1], 1a "not having the mind or feelings engaged" certainly sounds like GP's meaning and is the same definition given in [2] "not having the mind or feelings engaged".
[1] https://www.merriam-webster.com/dictionary/disinterested [2] https://www.merriam-webster.com/dictionary/uninterested
I've never used this tab. (Just opened it for the first time.)
It's cool, and I'm disappointed to see it go.
BUT: We should spend a minute thinking about the counter argument. Little and unused features can add cruft to a codebase, and significantly impede development. It's possible that hooks for corner cases and features can be so complicated that working around them becomes more burdensome than supporting the important use cases.
Case in point: When I was lead on Syncplicity, we had a corner case where a given folder on disk could be in multiple synchronized folders in the cloud. (Long story.) The problem was this corner case made many use cases, in the desktop client, significantly more complicated and bug-prone than needed. (What happens if you have different permissions to the same file?)
There was a point where I put my foot down (as lead) and said we couldn't support the corner case anymore. This lead to almost a year of two branches of the product, and daily merge conflicts between both branches. I had to put my foot down again (as lead) and push that we had to ship the version of the product that didn't have the corner case and stop working on two branches.
This makes me wonder if Github needs to cut back on corner cases and other little-used features in order to fix some maintainability issues?
OTOH if a feature not being widely used was grounds for its removal, they should turn excel into a list editor.
This scenario reminds me of a funny story posted on HN a while ago: https://memex.marginalia.nu/log/48-i-have-no-capslock.gmi (TL;DR; if you take this "usage based" feature removal logic to it's conclusion, a lot of important keys would be removed from computers/keyboards).
The GitHub search API seems to provide everything that is needed. It returns 30 repos per query and allows 30 * 60 * 24 = 43200 queries per day. So one could track the top 43200 * 30 = 1296000 repos.
That is enough to track all repos with more then 20 stars:
https://api.github.com/search/repositories?q=stars:%3E1000&s...
But maybe it has already been done? This looks like it:
You wouldn’t know unless you tried! Hopefully they didn’t invest too much into their MVP…
Microsoft endlessly tinkering with the product shows a lack of stability in it's lifespan, what if you adopt a new feature they add only for it to be removed in the next cycle. But they paid 7.5 billion dollars for the website, and need to justify the salaries of dozens of VPs of marketing and PMs, so here we are.
I can't imagine choosing GitHub except for cool points or if you're working very closely with code that isn't yours primarily.
For example: Things like SAML and SCIM are very important to enterprise customers and it feels extremely jank on GitHub.
Excel, MSSQL, vscode, c#.
Then you get turds like Teams..
Indeed, but GitHub's "social" features cater neither to enterprise customers nor to open source communities, but to a (hypothetical?) group of people that want a blend of software engineering and Instagram-style popularity chasing, with a bit of cartoon cuteness sprinkled on top.
I honestly found the introduction of the "achievements" section on user pages to be borderline insulting. I'm building cool stuff, not playing an RPG. Who does GitHub think their userbase is?
At least three investor groups are explicitly looking at lists of the most starred / forked projects and throwing money at those with "Instagram-style popularity", so we've reached the stage where people can trade in the "internet points" for real money.
Those emoji votes reduced a significant amount of the "+1" and similar low content comments which could take up significant space on a regular repo.
We could look at other issue tracking systems such as Redmine. Pulling up a feature that's in the next release https://www.redmine.org/issues/3088
> +1 It would be very good to get this, as we have to hide our estimations from some roles :(
> +1 on this one!
> +1
> +1 It would be great to have estimated times integrated in the allover times permissions system.
If you look at the comments on GitHub issues from before the expansion of emoji votes to what they are, there are fewer "fluff" comments.
The reasoning for this is in https://github.blog/2016-03-10-add-reactions-to-pull-request...
> While people have been able to include emoji in responses for a long time, using them as reactions resulted in a lot of noise. In many cases, especially on popular projects, the result is a long thread full of emoji and not much content, which makes it difficult to have a discussion. With reactions, you can now reduce the noise in these threads.
Now some people, to express support, react with "+1". Others react with "heart" or "rocket". How do you find the issues with the most popular support behind them? Do you sort by "+1" or by "heart"? On some issue trackers, one reaction type is preferred over another. On other trackers, reactions are mixed, and you find issues with 5 "+1" reactions and 40 "heart" reactions, and issues where it's the other way round. This is so hilariously bad that it almost feels like deliberate sabotage for laughs.
Imagine if HN, instead of upvotes and downvotes, had eight different ways to "react" to posts and comments, each with their own subtly different connotations. That's what GitHub implemented. It's something I would expect from a social network where people share photos of their cats, not from a system where software deficiencies are being discussed.
- is it free for my personal projects? - how many interesting libraries I may use are there? - does it offer a free tier of pipelines and things like that? - can I make private projects for free?
All the rest is noise. This is just me though.
"Trending" on social sites always seems to translate to, "here is popular thing that should become more popular because it's already popular."
The extreme preference for externally mediated measures of status never fails to amuse me.
This is exactly what i was searching a few weeks ago.
I was just looking at the list and saw this - https://github.com/EvanLi/Github-Ranking - anyone missing the rending feature might like that
Why do I need to see the React repo again and again?
The algorithm for deciding what is trending is to blame.
Many here are saying how much they like the feature.
I'd much prefer a "similar repos/projects/people" once I'm visiting a project or person I've _chosen_ to view.
I've already expressed my interest by visiting, why not exploit that?
but as others have alluded to, this will send some PM's kid(s) to college or help with the mortgage on their 2nd or 3rd property and should be a reminder that it's not great to rely on a company (especially a big co. with a wild track record like microsoft) for services, especially where important things like community or source code management are concerned
As someone who's building apps and actions to run on GitHub, I've always found the discoverability of apps to be lacking. The marketplace is nothing but a big list of things, in seemingly random order. Compare this to the Slack App "store" which has a much better discoverability and feel to it.
I which it had reviews, trends, new highlights etc, to make it easier to discover new apps, and for app developers like myself to get a chance to attract more users.
GitHub calls itself social coding, but trending fits in poorly with that. When I hit a problem that I think might be solved by open source, telling me that the TypeScript repo is trending gives me exactly zero information.
If we're honest, the Trending tab often seems to mean, "these projects went viral on HN/social media." And I'm not sure why they deserve extra attention, but it follows the general trend of social media being obsessed with perpetuating the Matthew Effect.
They want to remove it because it's probably expensive to run?
If they do this it must be for some other reason than upkeep.
I'm not sure, but trending tabs allow for growth hacking with tricks to get on the top by spammers.
What i prefer, is personalized trending profile instead.
And I am saying as a person who has always hated recommender systems at shopping sites/social media.
Thank you so much for creating this.
I suspect lany use it this way. Obviously compared to other tabs, it's going to be very low traffic. But in this case, traffic is a bad metric.
Also, how do you discover new and interesting projects in these days?
Maybe you can change it, I don't can't figure it out. Why is "Following" the default, I never need to know that.
I never used the "Trending" but it could be one of these cases where companies are measuring something, decides it's not being used, but fail to consider why that might be. Personally I don't see it being particularly relevant, but many seem to enjoy it.
To navigate to the "tab", which is just a page really. Click on "Explore" and then it's in the middle of the page, under the black menu. Or go here: https://github.com/trending
the product people is insane, it's an insane decision
Yes!?? Turns out the value is "not enough".
I never click on that and have starred no cool projects from there.
Seems like a totally reasonable product decision from my seat.
It encourages external crawling and aggregation of content hosted on their site. Seeing that their search feature already produces abysmal results, it only further obfuscates public repositories.
The same probably applied to shutting down Google Reader. But it's still brought up a decade later, because it hit the "right" group of users. These changes spend a lot of the goodwill built by Github.
Never knew it existed tbh
[x] Extend
[-] Destroy
The harder open source is to discover, the harder it will be to use. This is M$FT, after all.
Never underestimate Microsoft’s ability and propensity to fuck things up.
I remember when Skype was great, for example. We could easily cite 30 other such examples.