Comment Re:Sane choice (Score 1) 355
Pointers in anything other than the very lowest-level-touching-the-metal code are an abomination. They cause far more confusion and grief than they ever help. Yes, there are situations in which the best way to address a problem is to pass a pointer around. However, in this day and age of multi-gigabyte ram sticks, I'd rather bloat up a program's ram usage with maybe unnecessary copies of large objects than dick around with pointers.
You should talk to my students who just discovered how their 3x3 tic-tac-toe program had some "issues" when they tried 10x10. Understanding the difference between stack allocation and heap allocation, understanding the overhead of creating objects, understanding how to use structure sharing, understanding destructive mutation: all crucial for non-trivial programs. Multi-gigabyte ram sticks buy you nothing on real-world problems.
Nothing wrong with teaching pointers in Java or your other favorite modern language. They're just called reference types. But teaching malloc/free or retain/release, now that's crazy.