On Thursday 03 February 2005 01:30 am, Gabriel Sechan wrote: > From: "Andrew P. Lentvorski, Jr." <[EMAIL PROTECTED]> > > >No, I have always said to use the language that *fits*. > > I'd go a step further than this- the language that fits is the one you > have the most experience with. Programmed in perl for 5 years? Its best > for you. Done C for 20? Its best. Doesn't matter what the problem space > is. Sure, perl has built in regular expressins. C has libraries you can > download that do the same thing, an experienced programmer will have them > already, and there's really no difference between writing m/string/string/ > vs match(string,string). Need to write a GUI? Sure TCL has TK and Java > has Swing and AWT, but there's plenty of C APIs out there that are cross > platform too. Just use what you know and you're garunteed to finish it > quicker than you will in any other language. I've tried plenty of other > languages, and never really found that I was quicker even in their > specialized problem space than I would have been sticking to what I > previously knew. > > Gabe
Not the only issue. Code is written for an audience as well as to do something. What is the audience familiar with? That may be more important than what you know. boblq -- KPLUG-List mailing list [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
