On Tue, 2005-11-22 at 23:16 +1100, Crossfire wrote: > Ken Foskey was once rumoured to have said: > > The moral is use the correct language for the job. Performance is just > > a few thousand dollars in hardware away. Take $40K as your base (for > > example) and a server of $5K you need to save about 7 weeks work to pay > > for it. It is not a lot of time with 10 times the number of errors in > > your code. Bugs cost the time in development, correcting bugs in > > production code is far far worse. > > argh! no! *spew* > > Yes, C is rarely the right language. > > However, Perl, Python and Ruby are also often the wrong language. > [try finding variable name spellos or type parity problems quickly in > these languages - in a nice polite language like C, the compiler would > find it nice and quickly for you].
I find that test cases find these things extremely fast. And the find bugs that compilers cant :) Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
