GitHub language trends and the fragmenting landscape
A while ago, I wanted to get a little quick feedback on some data I was playing with, but the day was almost over and I wasn't done working on it yet. I decided to tweet my rough draft of a graph of GitHub language trends anyway, followed later by a slight improvement.
Context & Ripple Effects
The data drop lands at an odd moment for GitHub. The company spent March and April 2014 absorbed in the fallout from Julie Horvath's public allegations: Tom Preston-Werner placed on leave on March 16, an investigator's report on April 21 finding judgment errors but no gender-based harassment, and a CEO apology over transparency lapses on April 28. Berkholz's quiet, tweet-first release of rough language-trend charts runs on a different track — one built on the ambition GitHub staked out in late 2012, when it told the New York Times it saw itself as open source's future home.
On substance, the confirmed read of the numbers is fragmentation: language usage spreading across a more diverse landscape rather than consolidating behind one or two winners. The pickup matched the format — RedMonk, Berkholz's own tecosystems blog, and a handful of individual Twitter shares — so this traveled as an analyst-community data point rather than mainstream news, which suits a methodology argument more than a market event.
First-order effects
- GitHub's repository activity hardens into a de facto scoreboard for language popularity, extending the platform role the company claimed when it positioned itself as open source's home back in December 2012.
- RedMonk gets its fragmentation finding circulating among developers and fellow analysts before any polished report exists — the tweet-the-rough-draft method trades peer review for speed, and the pickup shows it worked.
Second-order effects
- Language communities and their corporate backers gain an incentive to optimize for GitHub-visible activity — new repositories, commits, contributors — because that is where rankings like this one draw their evidence.
- Popularity measures built on surveys or download counts come under pressure to explain divergence from repository-activity data, pushing methodology debates out of footnotes and into public arguments between analysts.
Third-order effects
- If the fragmentation pattern holds, 'the next big language' framing loses force: tooling vendors and hiring plans shift toward supporting polyglot portfolios rather than betting on a single winner.
- Measurement power drifts toward whoever hosts the activity — the platform owning the code graph effectively owns the narrative about language momentum, a structural advantage independent of any individual chart.
The trend: Programming-language measurement is shifting from curated indices toward raw repository-activity data at exactly the moment usage fragments into a long tail of coexisting languages.