We encourage, however, interested parties to perform their own analyses using other sources. GitHub and Stack Overflow are used here first because of their size and second because of their public exposure of the data necessary for the analysis. There are many potential communities that could be surveyed for this analysis.They are nothing more or less than an examination of the correlation between two populations we believe to be predictive of future use, hence their value. No claims are made here that these rankings are representative of general usage more broadly.To be included in this analysis, a language must be observable within both GitHub and Stack Overflow.With that description out of the way, please keep in mind the other usual caveats. We use the aggregated history to determine ranking (though based on the table structure changes this can no longer be accomplished via a single query.)įor Stack Overflow, we simply collect the required metrics using their useful data explorer tool.While this continues to have the caveats outlined below, it does have the benefit of cohesion with our previous methodology. Language is based on the base repository language.Our query is designed to be as comparable as possible to the previous process. We query languages by pull request in a manner similar to the one GitHub used to assemble the 2016 State of the Octoverse. The data source used for the GitHub portion of the analysis is the GitHub Archive. The idea is not to offer a statistically valid representation of current usage, but rather to correlate language discussion and usage in an effort to extract insights into potential future adoption trends.
#REDMONK STACK JAVA PYTHON JAVASCRIPTGRADYREDMONK CODE#
While the specific means of collection has changed, the basic process remains the same: we extract language rankings from GitHub and Stack Overflow, and combine them for a ranking that attempts to reflect both code (GitHub) and discussion (Stack Overflow) traction. As always, these are a continuation of the work originally performed by Drew Conway and John Myles White late in 2010. With the second quarter looming, it’s time for us to drop our first quarter bi-annual Programming Language rankings. Try our code patterns to help build the future of open source. From Java to Node.js, IBM remains at the forefront of open source innovation. This iteration of the RedMonk Programming Language Rankings is brought to you by IBM.
0 kommentar(er)
