The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
Poor choice of tools

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Vincent Foley

Posts: 512
Nickname: gnuvince
Registered: Apr, 2005

Vincent Foley is a hobbyist Rubyist.
Poor choice of tools Posted: Jun 2, 2005 9:41 PM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Vincent Foley.
Original Post: Poor choice of tools
Feed Title: Vincent Foley-Bourgon
Feed URL: http://www.livejournal.com/~gnuvince/data/rss
Feed Description: Vincent Foley-Bourgon - LiveJournal.com
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Vincent Foley
Latest Posts From Vincent Foley-Bourgon

Advertisement
I was reading a report about the OpenBSD hackathon, and something Daniel Hartemei, the author of pf, the OpenBSD packet filter, said struck me as very odd:



He was working on a large AMD 64 laptop, displaying a simple screen managed by OpenBSD's default fvwm window manager, coding in a vi window with mutt open to the side. "I don't install much other software," he explained when I asked him about his working environment. "I have too many machines, and once you get used to something you need it everywhere. It's too much work getting things customized on all these machines."


Emphasis mine. This struck me as very, very odd coming from a developer. Why wouldn't he use Vim or Emacs instead of the very plain and normal nvi? Vim and Emacs (or another programmer's editor for that matter) provides you with a lot of features that make writing software faster and more pleasant. He's coding in C, so he could have the following benefits if he were using Emacs:



  • Auto indenting
  • Syntax highlighting
  • Integration with make
  • Integration with gdb
  • Etags
  • Custom-made commands


Auto indenting and syntax highlighting can often help detect syntax errors rapidly, such as a missing comma, a missing closing paren, an unclosed comment, etc. Integration with make means that you can run make directly from Emacs, and Emacs can parse the error messages, and you can go to the faulty lines. Etags means that it's easy to keep track of the functions in your different source files. And finally, custom-made commands, I have a lot of those, he could automate some processes (such as testing pf features). So hearing that he uses plain vi is very odd to me.


And I don't buy the "too much work to customize" argument; all my third-party elisp code for Emacs is in a directory called ~/.elisp, so all he'd have to do to have a working environment would be to scp his .emacs and his .elisp directory. That would give him a more pleasant and more productive environment.

Read: Poor choice of tools

Topic: Paul Graham talk Previous Topic   Next Topic Topic: Gambit CodeFest in Full Swing

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use