Re:Apple Silicon M1: A Developer's Perspective
by fulafel on Saturday November 28, 2020 @12:47PM
(#25239049)
That article seems confused and/or misinformed on many points, on many levels.
As for the GP cited use case, there's no plausible way in which the compilers involved in the V8 build process would start using less memory due to their memory management machinery getting magically transformed by the hardware from tracing GC to refcounting GC, even assuming LLVM had been using tracing GC in the first place.
(Also the tracing GC memory overhead claims originating in Apple's marketing copy are way hyperbolic, modern tracing GCs don't require double storage used in "mark and sweep" GCs)
Re:Apple Silicon M1: A Developer's Perspective
by fulafel on Sunday November 29, 2020 @03:15AM
(#25243744)
Many memory hungry apps on Apple - Web browsers, compilers, photo/video editing, games, dev tools like vscode/electron/Jave IDEs/emacs/databases - are in this category.
As for the GP cited use case, there's no plausible way in which the compilers involved in the V8 build process would start using less memory due to their memory management machinery getting magically transformed by the hardware from tracing GC to refcounting GC, even assuming LLVM had been using tracing GC in the first place.
(Also the tracing GC memory overhead claims originating in Apple's marketing copy are way hyperbolic, modern tracing GCs don't require double storage used in "mark and sweep" GCs)