I ... don't think this is a good metric for 'popularity' but rather a good metric for stability/volatility. I would say that from working on a JS project, it's volatile af. You can use a package that will be abandoned tomorrow and you have no idea. Meanwhile, the languages near the "bottom" are quite stable languages to work in (as well as a pleasure). They even /almost/ noticed it themselves when mentioning golang 2…
Programming-language popularity by GitHub pull requests
21–30 of 73 posts
Re: Programming-language popularity by GitHub pull requests
#22I ... don't think this is a good metric for 'popularity' but rather a good metric for stability/volatility. I would say that from working on a JS project, it's volatile af. You can use a package that will be abandoned tomorrow and you have no idea. Meanwhile, the languages near the "bottom" are quite stable languages to work in (as well as a pleasure). They even /almost/ noticed it themselves when mentioning golang 2…
The author did narrow it down into what it mostly accurate represents though:
> Nevertheless, in my view, the number of pull requests is an important indicator of how much people are willing and capable of contributing to your software in the open source domain.
Re: Programming-language popularity by GitHub pull requests
#23Re: Programming-language popularity by GitHub pull requests
#24Lovely last sentence: believing c# being an underrated language. Very true, also public pull request are not friendly to dark matter enterprise software :)
Exactly - if you included my organization's private scope alone (an org of ~10 people), there would be 90 additional repositories and ~1.5k PRs/yr worth of C# action available to pad the stats.
Re: Programming-language popularity by GitHub pull requests
#25According to the graph here: https://madnight.github.io/githut/
Re: Programming-language popularity by GitHub pull requests
#26Clicking through to the underlying data, it seems that 2% of all code is written in Nix. I doubt that is the current state of the industry. For example, I doubt that 2% of programming jobs are for Nix codebases. For that reason, I am consuming a very large salt crystal alongside this information.
Better than TIOBE at least, which seems to have gathered a huge amount of popularity for no good reason. Their metric is just to search for "$LANG programming" in various engines, then assign arbitrary weights depending on the search engine used. It doesn't really measure anything, and has already been gamed intentionally, since it's so simple. Every metric is going to have its pitfalls, but at least this one seems t…
If you replace “has already been” by “can be”, I think all of that applies to this, too.
Re: Programming-language popularity by GitHub pull requests
#27Lovely last sentence: believing c# being an underrated language. Very true, also public pull request are not friendly to dark matter enterprise software :)
I recently got into c# and it seems really nice, but the "customs and traditions" of the dotNet world horrify me (eg: never write a function when you can write three classes instead)
Re: Programming-language popularity by GitHub pull requests
#28I ... don't think this is a good metric for 'popularity' but rather a good metric for stability/volatility. I would say that from working on a JS project, it's volatile af. You can use a package that will be abandoned tomorrow and you have no idea. Meanwhile, the languages near the "bottom" are quite stable languages to work in (as well as a pleasure). They even /almost/ noticed it themselves when mentioning golang 2…
Re: Programming-language popularity by GitHub pull requests
#29Re: Programming-language popularity by GitHub pull requests
#30I ... don't think this is a good metric for 'popularity' but rather a good metric for stability/volatility. I would say that from working on a JS project, it's volatile af. You can use a package that will be abandoned tomorrow and you have no idea. Meanwhile, the languages near the "bottom" are quite stable languages to work in (as well as a pleasure). They even /almost/ noticed it themselves when mentioning golang 2…