![]() ![]() For Stack Overflow, we simply collect the required metrics using their useful data explorer tool. ![]() 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.).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 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. 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. In the meantime, as a reminder, this work is a continuation of the work originally performed by Drew Conway and John Myles White late in 2010. We’ve been very busy over the past few months, but have found the time to run the requisite queries, the plot scripts and consider the results. Given that we’re days out from the second quarter, it’s about time for us to post our first quarter language rankings. More than 30 programming languages are supported! Join our community today and build your next application on any cloud with MongoDB Atlas. This iteration of the RedMonk Programming Language Rankings is brought to you by MongoDB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |