From wikipedia:
Puppet is a tool designed to manage the configuration of Unix-like and Microsoft Windows systems declaratively. The user describes system resources and their state, either using Puppet's declarative language or a Ruby DSL (domain-specific language). This information is stored in files called "Puppet manifests". Puppet discovers the system information via a utility called Facter, and compiles the Puppet manifests into a system-specific catalog containing resources and resource dependency, which are applied against the target systems. Any actions taken by Puppet are then reported.
Puppet consists of a custom declarative language to describe system configuration, which can be either applied directly on the system, or compiled into a catalog and distributed to the target system via client–server paradigm (using a REST API), and the agent uses system specific providers to enforce the resource specified in the manifests. The resource abstraction layer enables administrators to describe the configuration in high-level terms, such as users, services and packages without the need to specify OS specific commands (such as rpm, yum, apt).
Puppet is model-driven, requiring limited programming knowledge to use.
* Cut image into Gimp, cut little icon, export, google the image.
Using light blue, blue, grey blue and slightly lighter blue was not good design. I do understand it would be hard to use clearly defined colours with so many languages. My suggestion:
This would have been better presented if the user could select a language's icon and see its' data highlighted.
( I know you can't do that simply with an infographic - you'd need to create transparent overlays, or something. )
Something feels wrong with the data. For example. Q3/12 has abnormal amount of Pushes for all languages. Curious what causes the jump?
As someone who is color-blind, I really prefer people to combine symbols with color. Like you did with the active repos, except use the symbol in the key as well. That way if a color is close, I can check my guess against the symbol. Thanks!
> The number of active repositories, a useful proxy for the projects that people are working on right now.
This is better than looking at all of them like many of these stats do because it eliminates has-been languages.
> The total number of pushes per language as well as the average number of pushes per repository. These metrics are indicators of the rate of innovation occurring with projects being written in a particular language.
This is skewed towards developers who push small changes often, and even includes code shufflers, and ignores projects where the developer commits large samples at a time.
> New forks and open issues per repository, which also show active use and innovation.
Well written code has few issues raised.
> New watchers per repository, an indicator of developer interest.
This can be cheated by language promoters who run campaigns on twitter to double the Github watchers within a week. This stuff happens.
Javascript
Java
Ruby
Cascading Style Sheets
Python
PHP
C
C++
C#
Shell Script (bash et al)
Objective C
Go language
perl
Puppet
GNU RDoes this suggest that R usage is greatly underestimated, generally, then?
Also why did all of Perl get pushed in Q3/12? And every language got a significant peak that quarter? Is that a data error?