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

You can write an application that never frees memory and isn't leaking memory.



For some embedded applications, fixed memory regions work fine. For something like a compiler, not so much. Remember that you have to deal with chunks of data of unpredictable size. Even string literals might occupy megabytes. You could program your way around that, but most of the time these days, it's ok to burn memory (i.e. use GC) for the sake of development velocity.




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

Search: