Author: Vincent Diepeveen
Date: 03:19:02 08/01/03
Go up one level in this thread
On July 31, 2003 at 04:17:47, Graham Laight wrote: >On July 30, 2003 at 00:00:54, Robert Hyatt wrote: > >>Depends on your ultimate goal. If you are going to be a programmer, it is >>not the best way to go. If you program in Java for 4 years, then leave and >>go to work where they use C, you have a _long_ learning curve. You've never >>seen pointers, for example. >> >>We took a _lot_ of heat about that from companies like BellSouth. > >It sounds to me as though Java is better than C, because it prevents errors with >type. Wrong example. Learning a language like JAVA eats a lot of time from students. Before they have learned to program a bit in JAVA. How many years is that? On paper a few months of course, but reality is a few years. Then they leave your university just knowing Java. How are they *ever* going to work with imperative/objectoriented languages which use pointers? Any manager will before hiring them already figure out they can't do that. So they won't be hired for lucrative function offers. Only companies who completely write their stuff in Java they make a chance. So they can apply only for a few jobs which everyone wants... >For most businesses, the most pressing requirement is to make good code >cost-effectively - not to make super-fast code expensively. C is clearly going >to take longer to write and debug if it doesn't force type compatibility. > >Imagine you were a medical professor. You teach your students to treat illness >with medicine. The local doctors complain, saying that the standard methodology >in your area is to treat illness with leaches. Would you change your curriculum? > >It seems to me that this is analogous to what you have done with your >programming curriculum. > >-g
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.