Before trying any new technology, the first thing I do is try and find it's IRC room. If you don't know what IRC is, consider it a chat room for weird computer programmers. My first day trying node.js was also my first day in #node.js on irc.freenode.net. I was greeted by several friendly node enthusiasts and got lots of help getting my first node code working. Coincidentally, also on my first day, November 23, 2009, Debuggable starting running logs for #node.js.
In this article, I will dive into the #node.js log files, find out who the most active users are, and then follow their online handles to reveal who they are.
Disclaimer: These stats should not be used for anything important. All data-sources and tools used to make this are available here. Jump to the end of the article to learn how to crunch the numbers yourself.
Top 25 Most Active Users
Here is a raw dump of the most active users in #node.js by line count
|Nick||Number of lines|
sexy colors courtesy of pisg
Notable Top 25 Most Active Users
Part of what makes node.js great is it's community. The most active people in the #node.js IRC room are some of the most talented and prolific contributors to the project. I've taken the liberty to match up some of the most active online IRC handles to their real-life equivalents. The results are pretty amazing.
|Err...Marak Squires takes the #1 spot...that's me! I should talk less.|
|Isaac Z. Schlueter. Author of npm, Joyent Employee, Awesome Dude. Helped me on my first day in #node.js|
|Tim Caswell. Author of Connect, owner of howtonode.org, prolific node.js developer.|
|Micheil Smith. Changelog contributor and module developer hailing from Australia. Super friendly and helpful.|
|Mathias Pettersson, the unstoppable Swede. Winner of NodeKnockout ( several times over ). Author of several node.js modules.|
|Ryan Dahl. God-father of node. Joyent employee. Created node.js and double rainbows.|
|Alternate handle for ryah|
|Brian White. Mysterious man. Builds really slick node.js libraries such as ncurses and asterix.|
|Felix Geisendorfer. Owner of Debuggable. Author of several node.js modules. Maintains the #node.js logs|
|Matt Raney. Very tall, author of node_redis.|
|Elijah Insua. Nodejitsu contributor. Author of JSDOM and several other node.js modules.|
|TJ Holowaychuk. Author of ExpressJS and Connect. LearnBoost employee.|
|Alternate account for JimBastard.|
|Alexis Sellier - Prolific node.js contributor. Author of VowsJS and Cradle.|
|Rick Olson - Github Employee. Legendary Ruby on Rails developer. Possible super hero.|
Very Honorable Mentions
There are a few irc room users who came very close to making the top 25 most active and definitely should be mentioned. Their contributions to node.js have been amazing and they didn't have to talk a lot about it. :-)
|Matthew Eernisse. Yammer employee. Author of geddy.|
|Tom Hughes-Croucher. Community leader, author of several node.js modules.|
|Peter Griess. Facebook employee. Coder of hard-core node.js C stuff.|
|SubStack & pkrumins||1395 & 1379||http://github.com/substack
|James Halliday & Peteris Krumins.The StackVM guys. They release a lot of software, a lot.|
Crunching the numbers
For those who are interested where these numbers came from...
Getting the logs
To pull a copy of the #node.js logs from from debuggable, you can try this quick script I wrote here. There are also copies of the log files in this repo.
Cleaning the logs
I couldn't figure out what logging format was being used, so I wrote a quick script to convert the custom logging format into standard mIRC format ( which pisg can understand ). The clean log files are included in the node-stats repo
Use Perl IRC Statistics Generator. pisg is available for download here: http://pisg.sourceforge.net/index.php?page=download Once you have pisg downloaded, you simply run the pisg command and specify the log file or path you want to use.