Comments for i'm a lumberjaph

Comment on github explorer - a preview by franck

franck — Mon, 08 Mar 2010 13:08:37 +0000

@Yoan : I used the language breakdown API from github. For each repository, I fetch the main language for this repository, and I choose the language the most often used by a developer as is main language. Not really accurate, but good enough for what I want to do.

Comment on github explorer - a preview by Konstantin Haase

Konstantin Haase — Mon, 08 Mar 2010 12:58:54 +0000

I’m on the map! I’m on the map!

Comment on github explorer - a preview by Yoan

Yoan — Mon, 08 Mar 2010 12:05:50 +0000

How did you deal with people using different languages? I.e. I’m (Mr) pink but there is a mix between Ruby, Python, Erlang, PHP and JavaScript in my repos. Very nice work.

Comment on github explorer - a preview by elishowk

elishowk — Mon, 08 Mar 2010 09:48:25 +0000

Nice job. I hope you’ll publish more visualizations from this github crawls in the future.

Nevertheless, it’s disapointing NOT finding myself here ! How can this happen ?! After all the financial support I gave you to magnify Ruby and myself in your works :p

Comment on github explorer - a preview by Jonty

Jonty — Sun, 07 Mar 2010 21:45:14 +0000

I just spent an entertaining few minutes finding myself and other people I knew, with surprising results.

Lovely visualisation, thanks!

Comment on MooseX::Net::API by Clayton Scott

Clayton Scott — Mon, 21 Dec 2009 11:23:33 +0000

Wouldn’t the name MooseX::HTTP::API be more appropriate or do you expect to be able to handle more
networking protocols?

Comment on MooseX::Net::API by Michael Peters

Michael Peters — Sun, 20 Dec 2009 23:15:26 +0000

While I agree that it’s really annoying not to be able to install a module when offline (but really how often does this happen that the user has all the dependencies already installed, a copy of your code, but no network connection) and it’s annoying when tests fail because of different network setups, but if your module uses a network service IMO it’s important that it test that service.

If that service changes their API (on purpose or on accident) then your module will appear to work but in reality be broken. Who cares if your code is correct and your mock tests pass if it doesn’t actually work against the real service.

Comment on MooseX::Net::API by franck

franck — Sun, 20 Dec 2009 18:56:29 +0000

thanks for the advice, I’ve started to rewrite the tests.

Comment on MooseX::Net::API by Matt S Trout

Matt S Trout — Sun, 20 Dec 2009 18:38:48 +0000

Please please please don’t rely on live tests. Figure out a way to mock out the service calls, and bundle the dumb REST service with the dist.

Otherwise any user trying to install your module offline (whether on a plane/train or for some other reason) is going to be screwed - also HTTP proxies, DNS problems etc. can cause false positives on your testing.

I know this is annoying but it’s essential that your test suite tests your code, not whether the user happens to have a working TCP stack at the time …

– mst

Comment on Private and protected methods with Moose by Knut B.

Knut B. — Fri, 18 Dec 2009 15:21:44 +0000

Should builder Methods be made private using MooseX::MethodPrivate?
If yes:
It seems to me that they cannot be called anymore at object construction time:

The Myclass::_build_config method is private at generated method (unknown origin) line 156