No, it doesn't answer the question, it suggests more questions to ask to make an informed answer. It's just a short cautionary tale to make the user consider what type of app he/she is building, and to consider if significant activity within the app is, or not, likely part of the GC/JavaScript (or HTML/CSS) that would suffer in some cases vs local, native, code.
Personally, I tend to agree with the original article that GC is an expensive thing to put in most apps. BUT, you need to be pragmatic about determining if the additional margin of execution speed from not having a GC justifies the coding effort.
Having said that... you're right in that mostly this posting is to fulfill somebody's job requirements, rather than a substantial amount of content :-)
Comments
No, it doesn't answer the question, it suggests more questions to ask to make an informed answer. It's just a short cautionary tale to make the user consider what type of app he/she is building, and to consider if significant activity within the app is, or not, likely part of the GC/JavaScript (or HTML/CSS) that would suffer in some cases vs local, native, code.
Personally, I tend to agree with the original article that GC is an expensive thing to put in most apps. BUT, you need to be pragmatic about determining if the additional margin of execution speed from not having a GC justifies the coding effort.
Having said that... you're right in that mostly this posting is to fulfill somebody's job requirements, rather than a substantial amount of content :-)