2011-07-27

:q! your IDEs - use vi

The 80s called - they want their editor wars back. So here it is:

The participants have changed, however. I use vi myself, but I do consider every Emacs user a brother-in-arms. The picture may be different, if you're doing low-level systems programming, but in the unholy world of web-development the line is somewhere else.

It's between IDE users and real programmers uh, well - vi and Emacs users.

I am not going to talk about the up- and downsides of IDEs. Yes, they can do a lot useful stuff, yes they have auto-completion, nananana. They are taking away a Gig of core quite easily, but on today's machines it hardly matters, yada-yada, you know the story.

I am out today, to fight the myth that working with vi was like working with Window's Notepad. Or typing into cat(1). Or something like that.

Take this, myth: You are not true. Ha!

The first thing is: nearly everything of what the IDE makers sell as "features" can easily be handled by the typical Unix tools alone. So, even if I was typing into cat(1) on a Unix machine, I still would be much more productive than the world's fastest typist using Notepad on Windows.

That complex "Global Regular Expression Search (and Replace)" dialog window of Eclipse? That is grep(1) and sed(1). Batch file renaming? Known as rename(1) on Unix. Listing and navigating directories? Well, good 'ol ls and cd will do the trick, too. Building huge projects with just a single click? We use make(1) for that.

What remains on the IDE side? Yeah, automatic UML generation. Or code generation from UML. Or UML-ation of generated code. UML UML UML. (That, and bad XML-GUIs - as if XML wasn't scary enough on its own.)

On the other hand: no IDE in the world is as easily programmable or scriptable as Emacs and vi. No IDE has something like vi's :r! (open a shell, execute the following commands, read the result into the buffer). In fact, IDEs are not built to communicate with the exterior world at all. I think that is because* there is nothing out there* that would be worth communicating with - as is the case on Windows. And because there is nothing out there, IDEs have to provide every single stupid feature themselves.

So, IDEs actually emulate an operating system. A programmer's operating system, that is. Or, to put it another way: IDEs provide Unix on machines lacking Unix.

So why use the slow and heavy emulation? Why risk starting all over again learning to use all the features, if the vendor dies or that specific brand of IDE is unavailable? Why not use the real thing instead?

The standard:

Unix, and vi.



comments powered by Disqus