4 ms·
Tiobe can't be right. It has Assembly ahead of Ruby and right behind JavaScript. What??? Redmonk looks flawed too. I would expect GitHub to create a major samp
by claystu 11y ago
Tiobe can't be right. It has Assembly ahead of Ruby and right behind JavaScript. What???
Redmonk looks flawed too. I would expect GitHub to create a major sampling bias in favor of smaller, throwaway projects, and in fact, a quick search(1) on GitHub appears to show 2.2 million projects smaller than a kilobyte that have never gotten a single star. Should those be counted? Do they really reflect anything meaningful about the language's rank?
In my opinion, the only meaningful measure of a programming language worth quantifying from the net are StackOverFlow tags: they can be counted and read and provide a real reflection of the language's community without giving any special preference to language, license, or context.
Everything else is hopelessly subjective: whether or not the language maps well to a particular problem, whether it maps well to the way you like to program, and whether it fits into the ecosystem in which you plan to deploy it. You can't measure those with google searches.
(1) https://github.com/search?utf8=%E2%9C%93&q=size%3A%3C1+stars%3A%3C1&type=Repositories&ref=searchresults https://github.com/search?utf8=%E2%9C%93&q=size%3A%3C1+stars...
- ad-hominem 11y agoJust curious, but are there proper heuristics that are easily implementable to improve the ranking a language receives from github usage? For example, only count repositories that have more than 2 stars. I don't like cutting repos because they are under a certain size, because even a few bytes may be genuinely useful and widely used, but a repository nobody is looking at or really using is most likely a pet project. Maybe count only projects with > 2 stars (or forks?) OR projects with over a kilobyte of code? Perhaps such a project with no forks, no stars, but a lot of code might be a reference implementation or used in a talk or blog post or something but isn't useful other than to reference. I agree counting all github repos is a silly way to do it.