I've recently learned to stay away from #python. #rubyonrails is okay.
I've recently learned to stay away from #python. #rubyonrails is okay.
One time, I was talking with some people about how annoyed I was with not having a natural number type in Haskell. (Really, wtf?) It's annoying, but clearly not the end of the world--no other language I know has a natural number type either.
Can you guess what sort of response a complaint like this would have on another channel? At best, I would get some commiseration. But more likely people would either not care or actually get annoyed with me. I imagine similar reactions even to feature requests and complaints that are less "academic" than natural numbers.
So what happened on #haskell? Somebody went off and implemented a nice natural number library[1][2] right then and there--while I was still online, in fact. Pretty cool.
[1]: http://jeltsch.wordpress.com/2012/03/20/natural-numbers-in-h...
[2]: http://hackage.haskell.org/package/natural-numbers-0.0.0.0
Only issue is that there's a bunch of people whose answers could be solved by a quick search but still flood the channel with their questions.
That's just the nature of things though, it's hard to keep a handle on huge channels unless the channel ops are eternally vigilant. I was in #python some time ago, and there were good moments but there were lots of bad moments.
(I'm the Freenode Group Contact for #python,#python-*. If you have constructive criticism to make any of those channels better, I would be in a position to implement them.)
I will happily admit that any sufficiently large group will have some bad apples in it, but I certainly hope that we (I'm speaking for the operators of #python) have tried, are trying, and will continue to try, to limit them :) We've tried many things in the past, including crazy ideas like having two channels, but that ended up being counterproductive.