Reading over Steve's fine Q&A on yesterday's Java news I noticed the frequency that he mentioned an IRC channel, and not just our own, #redmonk. While we've had more success with #redmonk than any of us expected -- and we have the #redmonk community to thank for that, they're the ones who drive discussions there much more than us -- one of the big let downs for me is that many IT shops block IRC access. This means that many of my developer pals, architects, and others who in the confines of a fire-wall can't participate.
Which is not only a shame for us and #redmonk, but for those companies as well. For example, there was a highly interactive Q&A in one of Sun's IRC channels yesterday, and it's continuing into today. That is, if you were one of these fire-wall protected folks, you're missing out on the chance to talk directly with Sun people about open sourcing Java.
Instead, of course, I guess you can pay for information and access (or read our blogs ;>). That's a little over the top in selling this port un-blocking, but blocking IRC creates barriers to accessing the development community that companies could be directly profiting from.
There are web front-ends to IRC (I'm too inpatient to set one up) and there's even Campfire. But, there's nothing quite like the raw-firehose (and scale when it comes to Campfire) that IRC affords.
Sure, there's piracy and all sorts of hijinks to worry about, but come one, surely that's no reason to cut off an information flow that will give companies quick and free access to information and people who can help make them successful.