vijay jacob wrote:I think he is insane , he is trying to say we are going to program on the processor based.He seems to be system architect.
Not insane, just from a different planet.
But from a java programmers perspective ... where does these fit . Definitely a programmer should know all the memory management stuff.
I'd argue even that. One of the most stubborn problems with people from a C or C++ (or assembler) background is to get them to
forget about memory. In 99% of cases in Java it simply doesn't matter - and in a good percentage of cases where it DOES matter, it usually indicates a design or configuration problem.
Memory and its management is the
JVM's problem, not yours. Create objects; use 'em; let the GC collect 'em - it's really that simple - and obsessing about memory is a distraction. Furthermore, it's one that tends to lead to premature (or, even worse, micro-) optimization; and
that's a cure that is often worse than the problem.
As for your friend: Tell him he's playing with the big boys now, so things like register manipulation should be behind him. You can also tell him it's highly likely that, if it's needed, the JVM is far better at it than he is.
Winston