Re: Command line compiler
- From: Peter <p@xxxxxxxxxxxxxxxx>
- Date: 2 Jun 2006 19:19:19 +0200
Well, it has nothing to do with being a "real programmer". I'm about the
least macho programmer there is. I use whatever technology I'm fast,
competant and feel comfortable with. I see the benefits of both Linux and
Microsoft, and thoroughly enjoy both technologies.
But you (I hope you don't take offense) give off the aura of a zealot, and
absolute dogma is never a good thing.
When you see so many people using a technology, there's usually at least some
good in it. By cutting yourself off from something, as it _sounds_ you've
done with Unix tools, you make sure of a zero possibility of taking the best
from the technology and incorporating it into your own tools.
For my own part, I just really, really love vim. I seem to be faster with
vim than anyone else is with any other high level editor. I also find that I
like the flexibility of make (and ant, by the way).
I understand that it's possible to embed vim in VS. Someday I'd like to look
into how to do that. But for now, the simple and fast solution is to do
everything either in cmd.exe or with cygwin.
Anyhow, I advocate a moderate position with respect to all technology. I use
whatever I'm fast and comfortable with. I happen to love vim, Makefiles, and
command line tools.
You say that VS.net was a step backward. Perhaps other people think that
VS2003 was a step backward. I say: let everyone have their own opinions.
That's what makes the world so interesting. Imagine if everything were
homogeneous. What a bore that would be!
Pete
Joseph M. Newcomer <newcomer@xxxxxxxxxxxx> wrote:
Some people just don't believe in modern technology. I was apalled, when I returned to.
the University environment in 1990, that when I left in 1980, the state-of-the-art in
software development was the "cc" command and "cdb" as a debugger (one of the more
horrible debuggers to have ever been written). When I returned in 1990, the
state-of-the-art was the "gcc" command and "gdb" as a debugger (gdb copied all the flaws
of cdb; the solution of the free software community is to continue to propagate Really Bad
Ideas into perpetuity). And, as far as I can tell, there has been no progress in the
intervening 16 years in the Unix world. (In 1990, I was already doing better than this; in
fact, I ended up doing all my development on my 33MHz PC, which compiled faster than the
$60,000 IBM workstation in my office; besides, on my PC, the compiler worked, the linker
worked, and the debugger worked, all of which were rather important to me, and none of
which worked on the IBM workstation; the debugger on my PC [codeview] was of vastly better
quality as far as the user interaction than gdb, even if gdb had worked right).
There seems to be an aura of "real programmer" in the use of these rather primitive tools.
Frankly, I much prefer living in 2006 with 2006 tools than in 2006 with 1980 tools
(actually, the tools were probably about 1978). Of course, VS.NET kind of interferes with
my attitude, but that's because it is a giant step backward in IDEs.
joe
On Thu, 1 Jun 2006 15:21:31 -0600, "Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx> wrote:
I realize you are free to use whatever approach you like.Joseph M. Newcomer [MVP]
However, as someone who is comfortable with compiling in the IDE, I can't
imagine why you'd want to eliminate that in favor of a command line compiler
and makefile.
I recall the days where I created a makefile and ran nmake. All I can say is
"thank god those days are over."
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
- Follow-Ups:
- Re: Command line compiler
- From: Joseph M . Newcomer
- Re: Command line compiler
- From: Jonathan Wood
- Re: Command line compiler
- References:
- Command line compiler
- From: Peter Jay Salzman
- Re: Command line compiler
- From: Jonathan Wood
- Re: Command line compiler
- From: Joseph M . Newcomer
- Command line compiler
- Prev by Date: Re: DLL build error.
- Next by Date: message queues and buffered mouse clicks
- Previous by thread: Re: Command line compiler
- Next by thread: Re: Command line compiler
- Index(es):
Relevant Pages
|