> Changing to > Python/Java/Ruby/Lisp will not make you a better programmer, a faster > programmer, be easier to prototype in, etc. Even talking about language > "problems" like memory management in C-likes ends up beign wrong- if you > actually track defects, memory ones end up being a negligible percent, and > they tend to be the low cost ones to fix as well. You just exchange them > for a similar class of errors in Java/Python/other anyway. If you grab a > reference from a data structure in those languages, are you getting a deep > or shallow copy? The difference matters, and without studying the > individual structure you can't know. It tends to be a harder problem to > debug as well, althout thats probably my lack of experience in those > languages talking.
Are you saying that experts in any language pretty much develop things at the same rate? Are you saying that it is impossible to have a language automate some tedious task (memory management, variable typing) without introducing new problems that are just as bad? Are you saying therefore that a C expert using C and a Python expert using Python will both develop code at the same rate? How do you know? What are you basing these facts on? Chris -- KPLUG-List mailing list [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
