Comment Re:Emulated == always slower? (Score 1) 218
so using only what you need beats GC all the time.
"beats" is doing a *lot* of work here. There are literally hundreds of definitions of "beats"
And if "beats" = "better long-term run-time performance of specific high-memory, high-CPU tasks when the on-GC program is written by high-skill programmers who have had a year or two to find all the memory leaks", then I absolutely agree.
But my experience has been that situation is fairly rare. Granted there are a bunch of other very specific definitions of "beats" for which your statement could be considered true.
More to my point, I have found that claims of "A beating B all the time" often reveal a lack of understanding that problem domains are incredibly diverse, and the chance of a solution being the optimal one in all (or almost all) problem spaces is essentially zero. Being pro or anti-GC is as sensible as being pro or anti-hammer.
(And sorry for picking on your turn of phrase, but I have dealt with far too many projects where damage has been done by those who have morphed processes or tools or technological approaches into near dogma. I consider that tendency harmful and thus I found your sentiment worth of comment.)