Recently Jim Weirich, Bruce Williams, and Chad Fowler were chatting about how to improve the RubyGems platform-specific behavior, and realized that it would be really helpful to have more information about the install footprint of the Ruby community at large. That information is now available, thanks to an unusual RubyGem named Tattle.
According to Eric Hodel, the information collected will help speed delivery of the most-requested RubyGems feature, the
Tattle functions as a census tool. Install it by typing
Unsurprisingly, given Rails enthusiasts penchant for Macs, that platform is way in the lead, representing 44% of reported Ruby installations. Linux and Windows follow behind with 32% and 20%, respectively.
Full detailed results of the tally are available at http://tattle.rubygarden.org/.
According to Eric Hodel, the information collected will help speed delivery of the most-requested RubyGems feature, the
install --platform option.Tattle functions as a census tool. Install it by typing
sudo gem install tattle and then run it by its command, tattle. It will send a report back to a server containing basic platform information about your workstation and the versions of Ruby components installed on it. Running tattle report dumps the contents of the report to the console so you can verify it contains no personal information.Unsurprisingly, given Rails enthusiasts penchant for Macs, that platform is way in the lead, representing 44% of reported Ruby installations. Linux and Windows follow behind with 32% and 20%, respectively.
Full detailed results of the tally are available at http://tattle.rubygarden.org/.
Community comments
Rock on i386!!!!
by Clinton Begin /
Typo in install command
by Abhijit Nadgouda /
Did not install!!
by Biju Kunjummen /
Re: Did not install!!
by anjan bacchu /
Re: Did not install!!
by Sam Smoot /
Rock on i386!!!!
by Clinton Begin /
Your message is awaiting moderation. Thank you for participating in the discussion.
All 5% of you... :-)
Typo in install command
by Abhijit Nadgouda /
Your message is awaiting moderation. Thank you for participating in the discussion.
The command is
.Did not install!!
by Biju Kunjummen /
Your message is awaiting moderation. Thank you for participating in the discussion.
For some reason gem install tattle on Windows went into a nice little circular dependency for me, if it is the same experience for others on Windows, then probably the stats are distorted..:
gem install tattle
Bulk updating Gem source index for: gems.rubyforge.org
Install required dependency hoe? [Yn] Y
Install required dependency rubyforge? [Yn] Y
Install required dependency zentest? [Yn] Y
Install required dependency hoe? [Yn] Y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] y
Install required dependency zentest? [Yn] y
Install required dependency hoe? [Yn] Y
Install required dependency zentest? [Yn] n
ERROR: While executing gem ... (Gem::DependencyError)
Required dependency zentest not installed
Re: Did not install!!
by anjan bacchu /
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi There,
Nice to know about the windows troubles. Anyone else on Windows having these issues ?
BR,
~A
Re: Did not install!!
by Sam Smoot /
Your message is awaiting moderation. Thank you for participating in the discussion.
The circular dependency is not related to tattle specifically. See the following on comp.lang.ruby: groups.google.com/group/comp.lang.ruby/browse_t...
A check against duplicate gem names was apparently by-passed inadvertantly, and that brought down Hoe, and any gems generated with it.