vi in VisualStudio? Yeah!

It’s not religion, but it is close. My attachment to vi has only grown since I first really gave it a shot little over two years ago. Getting vi keybindings in a Java editor pushed me to finally scrap Eclipse in favor of NetBeans.

At work I’m a little more heavily tied down in terms of IDEs. Ditching VisualStudio is not easy at $EMPLOYER. Imagine the joy I just experienced when I discovered VsVim. Happy days!

Javadoc library

The great reorganization and unit test extravaganza continues. I’ve got most of my various and sundry projects migrated to use the NetBeans IDE. Also have pretty much everything migrated to use Maven. Which is very nice.

What I’ve been up to all morning. I would also post the accompanying SVN repos to go with these but, ummm, I have my web sites in the same browsable universe. And there’s some “sensitive” information therein.

Anyway, I can provide source if you’re interested. And I just know you are.

Eclipsed

I’ve gotten really tired of Eclipse pooping up my Maven projects. Like seriously bringing the buttstain. I’ve loved Eclipse ever since I started using it back in my time with the EVIADA project. I wrote a good bit of the UI for the Annotator’s Workbench using Eclipse.

I’ve used it ever since then too, even if the vi key bindings thing in the editor has never gone well. I’d been holding out for the Indigo release but the last week has seen me “reboot” my workspace twice already. When I code for fun, I want to code…not fight with an IDE.

But no more. Tonight I’m setting up a NetBeans environment. Damn the consequences! Hopefully the culture shock is not too great.