Here's the funny thing: my company is very generous in paying for dev tools. Most of the engineers are actually .net guys - they get premium MSDN subscriptions at like $4k per head. And, as you can guess from the title, we use Perforce for all source control. That's like another $800 per user or so.
My little dev group is working with Java. We just finished a big release of our project and now it's in that lull where I think I could switch the group over to IntelliJ. I used IntelliJ 4.5 back in university (hooray academic license) and I loved it. All I did was ask (in my 3rd week working at this company) and they didn't even bat an eyelash and got me a 3-version subscription. However, the project lead (and many others) use Eclipse because that's what they're used to. They've been using it for years because they didn't work for an employer before that was willing to pay for dev tools. As a result, they stick with Eclipse because that's what they know. Now that you have this open-source edition, their biggest complaint is gone - there's a free version, they don't really have a reason to not try it. So I wanted to switch the guys over. But... we use Perforce. I'm trying out the Eclipse project import, I'm writing a little how-to for my group, I'm willing to spend like the next 4 hours writing up how to use keyboard shortcuts for refactoring... but this lack of Perforce integration is killing me. It just won't help with the workflow. The other guys won't be able to use it, so I can't convince them to even try it.
I've got my 3-version subscription, but I'm actually moving to a .net group and won't be able to renew it. But you could get another 4 of these in like 1 week once I get the other guys hooked.
C'mon JetBrains - you open-source it to get more users, but then you exclude those that work in environments that are willing to pay for licenses like Perforce? Don't you think this policy is hurting you a little bit?