4 ms·

There is not much PHP on Github. It's the same reason there is no profanity it FORTRAN or COBOL in this graph. The author makes a terrible mistake: he does no

There is not much PHP on Github. It's the same reason there is no profanity it FORTRAN or COBOL in this graph. The author makes a terrible mistake: he does not normalize the graph relative to the total amount of code in each language. There's a lot of Ruby on Github, which is why you can find plenty of Ruby profanity. The graph is just about useless without this normalization.

BoppreH 16y ago
The author said he ripped the same number of commits from each language, so it's naturally normalized. The number of different projects ripped, on the other hand, could help skew the results of the unpopular languages.
- saraid216 16y ago
  There are maybe 10 to 15 ways the normalization doesn't manage to do what it's supposed to. Certain committers happen to use profanity more, for instance. Commit style and frequency. Tendency of programmers of language X to be acculturated somewhere that dampens their natural tendency to curse when frustrated. For instance, my style of coding means I branch off, commit early and often, with flippant and meaningless messages, and then I squash and rewrite my entire change as a single, formal entity before releasing it for coworker consumption. I curse up a storm in my commit messages, but you won't see any of them unless you look inside my computer before I delete the working branch. This is fun and funny. Nothing about it even starts approaching validity except for one statistic: "210 out of 929857", and even that gets shot down. The entire thing would have been better if he had included "hate" as a curse word.
  - chc 16y ago
    I think you've forgotten what was being discussed, because your objection isn't relevant. The claim in dispute is: "he does not normalize the graph relative to the total amount of code in each language".
notahacker 16y ago
That's rendered irrelevant by the author using a sample with the same number of commits in each language. Although I think it's fair to say the proportion of beginners and casual projects using source control and Github is probably lower for PHP than, say, Ruby.
- joblessjunkie 16y ago
  Yep, my bad, I did not carefully read the article. :-(

BoppreH 16y ago

The author said he ripped the same number of commits from each language, so it's naturally normalized. The number of different projects ripped, on the other hand, could help skew the results of the unpopular languages.

saraid216 16y ago
There are maybe 10 to 15 ways the normalization doesn't manage to do what it's supposed to. Certain committers happen to use profanity more, for instance. Commit style and frequency. Tendency of programmers of language X to be acculturated somewhere that dampens their natural tendency to curse when frustrated. For instance, my style of coding means I branch off, commit early and often, with flippant and meaningless messages, and then I squash and rewrite my entire change as a single, formal entity before releasing it for coworker consumption. I curse up a storm in my commit messages, but you won't see any of them unless you look inside my computer before I delete the working branch. This is fun and funny. Nothing about it even starts approaching validity except for one statistic: "210 out of 929857", and even that gets shot down. The entire thing would have been better if he had included "hate" as a curse word.
- chc 16y ago
  I think you've forgotten what was being discussed, because your objection isn't relevant. The claim in dispute is: "he does not normalize the graph relative to the total amount of code in each language".

notahacker 16y ago

That's rendered irrelevant by the author using a sample with the same number of commits in each language. Although I think it's fair to say the proportion of beginners and casual projects using source control and Github is probably lower for PHP than, say, Ruby.

joblessjunkie 16y ago
Yep, my bad, I did not carefully read the article. :-(