And the current editor is - Vim?
So, as I mentioned before, I'm looking for a new go-to text editor/IDE. So far, I've taken cursory looks at a few of the options. These include:
- PHPStorm. As I mentioned in the last post, I use PHPStorm at work. And while it's really good in a lot of ways, I'm not in love with it. On the up side, it's got great code intelligence and the VI-mode plugin is actually quite good. On the down side, it's a single-language IDE (well, not quite, but it's still got a limited set of supported languages). I guess I could just buy the entire JetBrains IDE suite, but I'm not crazy about switching back and forth. Also, PHPStorm is kinda heavy - like, Eclipse heavy - both in terms of memory footprint and, more important, conceptual weight of the UI. So while I don't dislike it, I don't really have any enthusiasm for it.
- Visual Studio Code. I initially liked the look of VS Code. It's got the cool Visual Studio intellisense, which is nice, and it seems to have a lot of extensions available. The Vim-emulation plugin seemed fairly good, but not great. The most popular PHP plugin, however, didn't seem to work out of the box at all. I'm not sure why, though it could be its wonky install process/implementation (apparently it's written in PHP). At any rate, I didn't care enough to look into it, though it might be worth taking a closer look at VS Code at some point.
- Atom. I liked the look of Atom. I read a little about the philosophy behind it and I really wanted to like it. But then I fired it up and tried opening one of my project directories and it didn't work. And by "didn't work", I mean that Atom actually crashed, consistently, on this particular directory. So that's a no-go. A quick Google revealed that it might be a problem with the Git library, which could possibly be fixed by changing the index version on the repo, but frankly I don't care. If I can't trust my editor to just open a directory, then I can't trust it at all. I mean, I don't even care if my editor has Git support at all, so I'm certainly not going to accept crashing if it sees a repo it doesn't like.
- Sublime Text. I've heard good things about Sublime. I used to work with several people who really liked it. Then I fired it up and immediately said, "What the heck is this?" The UI is pathologically minimal, except for a gajillion menu items and the stupid friggin' mini-map (which I didn't like in Komodo either). Configuration is done by editing a JSON file, but what the heck is with the weird out-of-box-experience? The UI is extremely minimal and customization is done by editing a JSON file, which is weird (to be fair, VS Code and Atom do that too, but it's more forgivable because they're free), and the plugin manager was immediately confusing. Seemed like getting used to Sublime might be a steep learning curve.
- Vim. Yes, you read that right - Vim. I was surprised too. Let me explain.
After trying out Sublime, my initial reaction was, "Geez, if I want something that complicated, why don't I just use Vim?" And then I stopped. And I said to myself, "Actually...why don't I use Vim?" Good Vim emulation is one of my must-haves, and no plugin is ever gonna beat the real thing. It's free, open-source, hugely customizable, has lots of available plugins, and is extremely well established.
The thing is, I knew Vim could be customized into a pseudo-IDE, but I'd never really thought of myself as a hard-core Vim user so I'd never tried it. But the truth is that I've been a Vim user for a very long time, and for the last few years I've been actively trying to pick up more Vim tricks for use in Vim emulation plugins. So while I didn't know an awful lot about customizing Vim, I'm very comfortable actually editing code in it.
And it turns out that actually customizing Vim isn't really that bad. Heck, there are even package managers for Vim now! There are also IDE-like configuration/plugin bundles you can install, such as spf13, but I quickly determined that those were too big and overwhelming. However, they are good as a source of ideas and settings to copy into your own custom
~/.vimrc file. That's actually part of the beauty of Vim - despite the fact that Vim script is a little weird and the configuration is in no way intuitive, there's enough information already out there that it doesn't really matter.
So over the course of a week or so, I pulled out some of the more interesting settings from the spf13 config, found a selection of plugins that I liked, and got myself a nice, functional Vim setup. I even set up some symlinks and file syncing so that I can have my setup synchronized between home and work.
Is it perfect? No, but nothing ever is. But so far, it's working pretty well. And what's more, I actually enjoy using it. It might not have the power of a specialized IDE when it comes to the more advanced features, but it's got a heck of a lot of power in general. And the amount and types of customization you can do are amazing. With a little effort, you can really shape the editor to your workflow, which is a thing of beauty.
You can reply to this entry by leaving a comment below. You can send TrackBack pings to this URL. This entry accepts Pingbacks from other blogs. You can follow comments on this entry by subscribing to the RSS feed.