Why use that primitive Vi?

Sometimes after leading some customer through a vi session to fix their problem I'll hear something like this:

"Why does (Unix/Linux) make things so hard? That 'vi' is so primitive - they should have a word processor!"

Of course there are Linux and Unix word processors - plenty to choose from. There are even text editors that would probably be easier for an unskilled person to use. But even if the person on the other end of the phone line said "I know how to use Joe" (a common and fairly user friendly text editor), I'd still probably say "I'd rather lead you through it with vi."

Why? Well, first off, it's me that is leading you through the necessary keystrokes, and it's one heck of a lot easier for me to give precise instructions in an editor I know cold than to say what I want accomplished and have it get screwed up. If the person at the other end types exactly what I tell them to type, I know what the results will be: I don't have to wonder. If they can't follow directions closely, it's also easy for me to know that they weren't paying attention, and it's usually easy to get the error fixed and get them back on track and touching no keys until I say to.

But it's more than that. With Vi I can control what happens and where it happens very specifically (see Vi Primer to learn a bit about vi if you need to). If I need exactly seven characters deleted, I can say "Type 7 and then x". I don't have to worry that the person at the other end will lose count and trash eight characters: vi will do just what I say. I can delete exactly four lines, I can specifically delete or change line 378, I can in one command change every occurrence of "foo" to "bar".. you get the picture. Like most other Unixy things, it's about having CONTROL. You don't get that kind of power with a word processor or a "user friendly" text editor.

Unfortunately, I don't usually have the time to explain all this to someone who complains about primitive editors. They probably wouldn't be interested anyway, but now that I've written this, maybe I'll just send them a link in email.. just so they can understand why I use that "primitive" vi.

Click here to add your comments




Fri May 23 20:53:45 2008: Subject:   drag


Agree with them. Say that you like the syntax highlighting of Vim much more (even if it's a lie)




Sat May 24 09:55:15 2008: Subject: vi   joe


How many hours y spent with my old SCO´s vi.....

It´s hard to use, but it do as exactly i meant....

(as i become older y love more vi and less use msword)

Regards anthony from patagonia argentina...



Sun May 25 14:43:29 2008: Subject:   Lantrix
http://techdebug.com

I use vi every day at work, but prefer vim on my own machines (gvim on win32 where I must). I'm slowly converting all my geek friends one at a time.

Even when I use apps like textmate which are nice - I always miss the simple elegance of vi (and vim).



Thu Jul 31 05:28:15 2008: Subject:   AlanHaggaiAlavi
http://alanhaggai.org

I use vi(m) for almost all editing purposes. It is just the overhead of initially learning the vi(m) editor that gives it the term `hard'. However, after mastering it, we have a heads up over everyone using other editors. It simply is worth the effort.



Thu Aug 21 20:27:33 2008: Subject:   SirTuna
http://www.argentum.ath.cx

I'm still a pico guy. Lightweight, but not terribly cryptic - no frills, really. Though, I have friends that swear by emacs... *shudders*



Fri Sep 26 13:02:01 2008: Subject: vi is there   tweetiepooh


Also vi is always there; HPUX, Solaris, Linux vi is there. (I needed to faf around a bit on Gentoo to get it there during install).



Fri Sep 26 21:09:53 2008: Subject:   TonyLawrence


Yes, vi is almost always there. In the old days, you couldn't depend on emacs being installed, but you could depend on finding ed and vi..

---

Macworld Mac Security Superguide $9.99

---

Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments

If you want a picture to show with your comment, go get a Gravatar

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.