ReSharper isn’t a fat slow pig anymore
I know it’s been a while since my “JetBrains Resharper is a fat slow pig” post, and I thought it was only fair to give an updated of my current impressions. My friend Jonathan wrote on his blog that I had recommended it to him, which confused some people. I’m currently using the latest service pack for the 2.0 version, and I haven’t used the 3.0 version.
I’ll be the first to admit that they fixed pretty much all of the performance issues I was seeing. It installs quickly, and only slows down Visual Studio the first time you run it. It does some kind of menu re-building that is then cached. I have been very happy with the performance, and it blows away the refactoring that Microsoft decided to hack into it.
I love ReSharper not only because of the quick refactoring, but the indispensable tips and warnings it gives as you write your code. It easily pays for itself because of the bugs that it points out. I honestly don’t know how I would live without it.
The only complaint I’ve had is that I’ve see it get whacked, and thought that all my code was an error. I had to uninstall it from a machine because of that. Luckily, I don’t use that machine for development any more. I thought it was an uncommon occurrence, but Jonathan said he ran into the same thing. He even called support to resolve the issue, and they were apparently no help.
Sure, it’s not perfect, but if you’re a serious developer, you shouldn’t be without it.