Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Top 10 Programming Languages On GitHub, Over Time

Posted by timothy on from the diagonal-lines dept.

An anonymous reader writes with a link to VentureBeat's article on the information that GitHub released this week about the top-ten languages used by GitHub's users, and how they've changed over the site's history. GitHub's chart shows the change in rank for programming languages since GitHub launched in 2008 all the way to what the site's 10 million users are using for coding today. To be clear, this graph doesn't show the definitive top 10 programming languages. Because GitHub has become so popular (even causing Google Code to shut down), however, it still paints a fairly accurate picture of programming trends over recent years. Trend lines aside, here are the top 10 programming languages on GitHub today: 1. JavaScript 2. Java 3. Ruby 4. PHP 5. Python 6. CSS 7. C++ 8. C# 9. C 10. HTML

3 of 132 comments (clear)

  1. Re:i think it shows trends in GitHub's demographic by tkrotchko · · Score: 4, Interesting

    I agree. If you look up what programming language experience companies are looking for, you usually end up with two very unsexy choices: Java and C.

    http://spectrum.ieee.org/compu...

    Javascript will continue to be popular if only because it's becoming the defacto standard for cross-platform mobile development.

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
  2. Re:Programming? by Gondola · · Score: 4, Interesting

    Next up: the TXT, NFO, INI, and CSV programming languages!

  3. Re:i think it shows trends in GitHub's demographic by Antique+Geekmeister · · Score: 3, Interesting

    A great deal of professional code is published: it's key to the Apache foundation and the Free Software Foundation. And a great deal of the more straightforward being published as "C++" for lightweight applications is standards compliant C. I just went through a similar issue with a job applicant who wrote backend website processing: That person's code had _no_ C++ elements in it, written for the simplest and most reliable compilation. It was very lightweight, the libraries it required were very stable, and it had _no_ dependency confusion common to the "overloading" of C++ functions. I was quite pleased with their code.