View Single Post
  #19   Spotlight this post!  
Unread 15-03-2007, 22:59
Greg McCoy's Avatar
Greg McCoy Greg McCoy is offline
boiler up!
FRC #3940 (CyberTooth)
Team Role: Engineer
 
Join Date: Feb 2002
Rookie Year: 2002
Location: Kokomo, IN
Posts: 484
Greg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond reputeGreg McCoy has a reputation beyond repute
Send a message via AIM to Greg McCoy
Re: Unix programmers: vi or pico?

vi and pico are intended for completely different things. Pico is really meant to be as easy as possible for people who aren't that comfortable with computers/command line interface (i.e. pine, etc.) vi (and emacs, if you're in that camp) are so much more powerful than pico/nano it's like comparing a moped to a F1 car. It might be a pain at first, but it's worth knowing how to use it. Having a search facility that can handle regular expressions and a decent macro recording capability are hard to give up once you know how to use them. vi has been a part of every Unix/Unix clone for pretty much forever.

Quote:
Originally Posted by meatmanek View Post
Nobody really should be using either anymore - both are outdated.
The command line interface is FAR from dead...it just depends on what you are doing. I find it hard to believe anyone gets very far as a programmer/computer engineer without knowing how to do basic tasks with a CLI.

Personally, I use TextMate (a nice GUI editor for OS X) and vi. Both have their merits. I use vim for something almost every day.