When the memory allocator works against you

Re:When the memory allocator works against you by mgottein on Sunday March 12, 2017 @01:12PM (#13851710)

I personally believe one of the biggest reasons for the popularity of managed code is GC. Manual memory management is pretty hard to get right, even the C++ stl offers reference counted pointers as a form of automatic memory management

[ Parent | on HN ]

Re:When the memory allocator works against you by dbaupp on Sunday March 12, 2017 @01:25PM (#13851780)

I think that is a rather common belief... "Managed" is exactly referring to automatic memory management meaning the defining feature of the category is literally GC.

[ Parent | on HN ]

Re:When the memory allocator works against you by jstimpfle on Sunday March 12, 2017 @03:28PM (#13852537)

Wikipedia disagrees. "Managed code is computer program source code that requires and will execute only under the management of a Common Language Runtime virtual machine, typically the .NET Framework, or Mono. The term was coined by Microsoft."

[ Parent | on HN ]

Re:When the memory allocator works against you by dbaupp on Sunday March 12, 2017 @05:47PM (#13853318)

Huh. By that definition Java isn't managed, which seems to be missing the point and not as nearly useful as a broad category like everyone outside the Microsoft ecosystem uses it. That said, even if "CLR" is sensibly replaced with "CLR, JVM or similar", it does seem like I have the etymology/definition wrong, thanks.

[ Parent | on HN ]

Re:When the memory allocator works against you by jstimpfle on Sunday March 12, 2017 @06:14PM (#13853458)

Yes, I also think of Java as "managed". But the common idea of "managed" seems to be more than only "garbage collected".

[ Parent | on HN ]