Context Navigation

Changes between Version 1 and Version 2 of Ticket #65415, comment 28

v1	v2
5	5	As for garbage collection: In the very early days of the industry - before the days of multi-core CPUs, when speeds were still measured in MHz - GC did have a tangible impact on performance. And it could be quite intrusive, depending on the language/system.
6	6
7		Since then, GC techniques have evolved so far, that they're actually more efficient than C code that explicitly calls ~~malloc() and free()~~. (Or the `new` and `delete` operators in C++, if you prefer.) That's because memory deallocation and reclamation can occur in the background - and in a batched, highly-efficient manner - such that it's inconsequential.
	7	Since then, GC techniques have evolved so far, that they're actually more efficient than C code that explicitly calls `malloc()` and `free()`. (Or the `new` and `delete` operators in C++, if you prefer.) That's because memory deallocation and reclamation can occur in the background - and in a batched, highly-efficient manner - such that it's inconsequential.
8	8
9	9	That's why even the newest languages like Google's Go - which was designed from the ground up as a C/C++ replacement - use GC for memory management. It's really that good!