On Tue, 2011-03-22 at 12:03 -0400, Nathan Hamiel wrote: > > Quite many?
I can't even recall how many packages source code I have seen that in. Lots of GNU software and other FOSS. I can't recall offhand, but I believe I have seen that in glibc, kernel drivers, and other things that are pretty much everywhere. > How large are these organizations? Big, globally used software. Allot of this software is used by many big organizations. Which would make its install and user base immense. > The enterprises I deal with typically use Vim or Emacs for editing > config files or other misc systems admin stuff. Never for things like > developing enterprise applications. It just seems pretty small time to > me. Thats when its broken down into departments and people doing coding never touch systems. Usually when a system administrator goes to code, they do it with things available on the system at the time. Not always do they have access to an IDE or time to go install one to make various changes. It all depends, but I would say in quite many large companies. Most coders are using IDE's, but not all, and there is still many who will use other things. Keep in mind if your programming, testing, or developing for embedded systems. You don't always have all the things you would on a full blown machine. > I actually toned it down a bit. I had the word stupid in there instead > of not smart and I stand by it. I agree with stupid more than smart. Even smart people will make stupid mistakes :) > VI/VIM is not made for what these people are using it for. Not to > mention there is no code intelligence, code completion, or any of the > other useful features of an IDE. The issue that made it in production > wouldn't have made it there if an "real" IDE where being used. I would not be surprised if there are modules or plugins which extend VI/VIM to give it that functionality. Thats the biggest aspect of Emacs is its extensibility. People integrate that with way to much stuff IMHO. > Let's say you are a singer and that is your job to sing in a band. > It's the equivalent of giving you a megaphone (VI) or a microphone > plugged in to a PA system (IDE). They both amplify your voice but with > a microphone you can always turn up the volume, add effects, or get > bigger speakers (IDE plugins). With a megaphone sooner or later you > are going to blow out your voice. There is something to be said about > using the right tool for the right job. You have all the right tools in place, but if the user is not skilled as to how to operate the tools. The result will be less than ideal either way. Just the same I have seen people do amazing things with a very limited tool set. The man makes the tools, not the other way around ;) > I was referring to the code intelligence of an IDE, which would have > indicated a problem with that particular line. Yes but that can vary not all IDE's are the same :) > Either way, it's a breakdown of process. I totally agree, they failed in several ways, all process related. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
