<p>It is all personal preference and lessons learned. In a past life, all the Navy contractors I interacted with had at least a working knowledge of vi. Too many times laptops would not make it through customs, lost overboard, <insert random unforseeable circumstance>, and emacs and vim was not always a guarentee on the high side. I have yet to run into a *nix box without vi and too many times I have had to crank out perl scripts using only vi.<br>
I always recommend at least working knowledge.</p>
<p>Simmons</p>
<p>This message was sent from my android phone.</p>
<p>On Aug 27, 2010 5:49 PM, "Chuck Cole" <<a href="mailto:cncole@earthlink.net">cncole@earthlink.net</a>> wrote:<br type="attribution">> <br>> <br>>> -----Original Message-----<br>>> From: <a href="mailto:tclug-list-bounces@mn-linux.org">tclug-list-bounces@mn-linux.org</a><br>
>> [mailto:<a href="mailto:tclug-list-bounces@mn-linux.org">tclug-list-bounces@mn-linux.org</a>]On Behalf Of Adam Morris<br>>> Sent: Friday, August 27, 2010 4:48 PM<br>>> To: TCLUG Mailing List<br>>> Subject: Re: [tclug-list] Linux and on topic<br>
>><br>>><br>>> On Fri, Aug 27, 2010 at 04:03:41PM -0500, Chuck Cole wrote:<br>>> > In my experience (considerable: with several hundred<br>>> programmers doing stuff<br>>> > ranging from supercomputing OS and language stuff, to IT to embedded and<br>
>> > secure avionics, and so on... ) those who do kinda small single-thread<br>>> > stuff like I/O intensive IT stuff will prefer vi, while those<br>>> (eg, MIT PhDs)<br>>> > who do huge and inter-related stuff will prefer Emacs. Like<br>
>> most else, it's<br>>> > context-dependent. No surveys, except herding such cats on aerospace<br>>> > contract projects and programs which have formal reviews,<br>>> deliverables, and<br>
>> > so on.<br>>> ><br>>> ><br>>> > Chuck<br>>><br>>> If by huge and inter-related you mean projects with 800,000+<br>>> lines of code, I definitely can attest that I've seen plenty of<br>
>> people use Vi on projects like that (including myself).<br>>><br>>> I'm wondering if a large bit has to do with schooling and where<br>>> you work. I know that at my school Vi (and for those who<br>
>> couldn't cut it, Pico) was the editor of choice of everyone<br>>> because our Professors used it. I can understand the use of Vi<br>>> in the SysAdmin world because Vi is generally guaranteed to be on<br>
>> any Unix system, whereas Emacs isn't, but for programmers I'm<br>>> betting if you go to a place out of school that is using Vi for<br>>> programming, you'll probably end up using Vi.<br>>><br>
>> -Adam<br>>><br>> <br>> <br>> Is your experience from aerospace where there are formal requirements,<br>> juried reviews, etc, or from a context of individual contributors working to<br>> self-imposed or locally imposed requirements? In satellite signal<br>
> processing, secure comm, life-critical avionics, and so on, vi is seldom<br>> used on "big things". I'm referring to real-time life critical cases, not<br>> school or IT or academic med. In that aerospace experience base, vi is much<br>
> less likely, but project teams may select "team tools" based on particular<br>> tasks, people, and so on.<br>> <br>> <br>> Chuck<br>> <br>> <br>> _______________________________________________<br>
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>> <a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>> <a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
</p>