Hello...
What about garbage collection?
Read what said Chris Lattner:
"One thing that I don’t think is debatable is that the heap compaction
behavior of a GC (which is what provides the heap fragmentation win) is
incredibly hostile for cache (because it cycles the entire memory space
of the process) and performance predictability."
"Not relying on GC enables Swift to be used in domains that don’t want
it - think boot loaders, kernels, real time systems like audio
processing, etc."
"GC also has several *huge* disadvantages that are usually glossed over:
while it is true that modern GC's can provide high performance, they can
only do that when they are granted *much* more memory than the process
is actually using. Generally, unless you give the GC 3-4x more memory
than is needed, you’ll get thrashing and incredibly poor performance.
Additionally, since the sweep pass touches almost all RAM in the
process, they tend to be very power inefficient (leading to reduced
battery life)."
Read more here:
https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160208/009422.html
Here is Chris Lattner's Homepage:
http://nondot.org/sabre/
And here is Chris Lattner's resume:
http://nondot.org/sabre/Resume.html#Tesla
Thank you,
Amine Moulay Ramdane.