> I'm even working up the courage to dive into vim.

If you're going to be using something 10 hours a day for who knows how many years, definitely take the time to get to know the best tools, which to me are still Emacs and ... I'll grudgingly admit, Vim.

Interesting how the editor wars seem to have ceased due to the prevalence of other editors. It used to be emacs vs. vim, now it seems to be emacs and vim vs. everyone else. (I completely agree, from the vim side).

I've noticed this too over the past few years that I've been dipping my toes in these waters. I just started learning emacs after working in vim for the past couple of years. Not an attempt to switch so much as to have another tool on my tool belt. Plus I don't want to be handicapped if a pairing opportunity arises.

You could also try emacs. I've used vim for years and switched to emacs recently (well, with the fantastic emacs evil plugin, that emulates all vim keybindings), but coming from Sublime emacs may be easier to get into as it is not modal. Also, it still has a ton of fantastic plugins.

That's a complicated build process, even for someone who already knows his way around Go. It wouldn't hurt to have a few binaries for those who just want to see what it looks like

do you know what GPU driver you're using? many times, i have come across people still using the framebuffer driver..

switching backing and forth between radeon and fglrx all the time, depending on which one is giving me the most headaches at the time

are you sure fglrx gets loaded properly? i'd give it a go and poke around your Xorg log file, and ensure everything is as expected - any radeon from 2006+ should be able to handle unity and sublime..!

Do it, but steal somebody else's .vimrc that maps leader and some basic switching between buffers/tabs.

Join the ranks of VIMmers! One of us! One of us!