I find the complete lack of Go surprising.
Go is a new language so not that surprising. It is also over represented here on HN. You don't see Go jobs in the wild for example.
GitHub Language Trends
21–30 of 68 posts
Re: GitHub Language Trends
#22GitHub is slowly starting to reflect the software world at large, although the true picture is Java and C leading by a huge, huge margin. I don't expect GitHub to ever fully reflect that, as most Java shops, and nearly all C shops, would never host their code on GitHub.
Re: GitHub Language Trends
#23FWIW many projects written in web languages like PHP seem to be treated as javascript by Github because they also have javascript code (which happens to be more significant / larger than the underlying code). It's unfortunate that there is no way to specify the primary language of a project. The Github language system is also somewhat unpredictable: https://github.com/SheetJS/test_files seems to alternate between App…
If a project mainly consists of JavaScript it should be a JavaScript project, no?
Re: GitHub Language Trends
#24I find the complete lack of Go surprising.
Except for HN, at the enterprise level, Red Monk main customers, no one cares.
Re: GitHub Language Trends
#25FWIW many projects written in web languages like PHP seem to be treated as javascript by Github because they also have javascript code (which happens to be more significant / larger than the underlying code). It's unfortunate that there is no way to specify the primary language of a project. The Github language system is also somewhat unpredictable: https://github.com/SheetJS/test_files seems to alternate between App…
If a project mainly consists of JavaScript it should be a JavaScript project, no?
[deleted]
Re: GitHub Language Trends
#26Not sure if it's reasonable to make this call, but it seems the dynamically typed languages have significantly higher percentage of issues overall.
It could be that dynamic languages have a lower barrier of entry, which encourages many more people to fork the code, find bugs, and make pull requests. It's easy for a PHP guy to find and report bugs in a JavaScript project. It's not so easy for a JavaScript guy to find bugs in a C++ project.
Re: GitHub Language Trends
#27FWIW many projects written in web languages like PHP seem to be treated as javascript by Github because they also have javascript code (which happens to be more significant / larger than the underlying code). It's unfortunate that there is no way to specify the primary language of a project. The Github language system is also somewhat unpredictable: https://github.com/SheetJS/test_files seems to alternate between App…
If a project mainly consists of JavaScript it should be a JavaScript project, no?
Well, to take an example: I work on the Mozilla Developer Network (MDN). MDN is mostly a wiki, and the underlying codebase for that is all in Python. There's also the Demo Studio, which lets people upload web technology demos, and that's Python too.
But the wiki also has an embedded script-ish language (letting people create macros/templates for specific purposes and re-use them across multiple articles). That's JavaScript-based, and so is implemented in node.js. And there's a WYSIWYG editor for the wiki pages, which is a couple of MDN-specific plugins we've developed, plus off-the-shelf components (the editor + jQuery, which we also use for a few other things on-site).
So MDN is a Python project with a couple JS utilities attached. And if you set up a local copy, you can pretty easily see that Python is by far the heaviest-used language. But due to the way GitHub counts and reports statistics, it shows up as a JavaScript project.
To pick on an easy example: the copy of jQuery we have in our repository weighs in at just over 9,000 lines. So just having jQuery means you need to write over 10k lines of code in order to get the "real" language of your project recognized.
Re: GitHub Language Trends
#28I don't know this is a good indication of trends. As the article (somewhat shallowly) shows, there are stories behind of these graphs. Ruby has probably just settled to a normal position post early adopter. Shows that Ruby is still strong. Javascript is probably building the sorts of libraries that other languages already have. These guys have had a lot of work to do.
Ah, it is only on internet forums where someone can argue that a sharply downward trending graph shows that a language is 'still strong'.
Re: GitHub Language Trends
#29I don't know this is a good indication of trends. As the article (somewhat shallowly) shows, there are stories behind of these graphs. Ruby has probably just settled to a normal position post early adopter. Shows that Ruby is still strong. Javascript is probably building the sorts of libraries that other languages already have. These guys have had a lot of work to do.
Ah, it is only on internet forums where someone can argue that a sharply downward trending graph shows that a language is 'still strong'.
"GitHub is a specific community that’s grown very quickly since it launched [writeup]. It was not initially reflective of open source as a whole but rather centered around the Ruby on Rails community"
Github has moved out of a niche over the past five years, and the graph demonstrates that.
Re: GitHub Language Trends
#30> Violating all expectations and trends, new Java users on GitHub even grew as a percentage of overall new users, while everything else went downhill. This further supports the assertion that GitHub is reaching the enterprise.
This is more likely to be due to the rise of Android since 2009.