Hacker News new | past | comments | ask | show | jobs | submit login

Why Java though? Java uses object handles, not raw pointers, so a stop-the-world GC in a JVM can relocate and defragment memory whenever it wants.



Java because GC lures people into a false sense of security. You can still leak memory by failing to release references here and there and in a heavily used system this can rack up quite considerably over a 24 hour period and it's often more pragmatic just to reboot the application than get somebody to fix it. I suppose most other languages/environments could suffer this but with Java it's drummed into you from the very start that "you can't get memory leaks" so people just don't worry about those things.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: