Google Closure and GWT both do exactly that - they use static analysis to cull code which never gets called. You can't use them with standard JS libs though - JS code needs to be specially marked up to use that feature in Closure, and GWT development is in Java.
GWT takes the idea one step further - the code splitting functionality lets you define split points, and code that only ever gets called behind the split point does not need to be downloaded on page load, but can instead be downloaded when that split point is first reached.
3x would cause antialiasing artifacts for apps with images optimized for 2x retina displays. Apple decided to wait for pixels to be 4x smaller before jumping to a higher resolution, so they must think these artifacts are unacceptable. Therefore, the logical next step is 4x displays with 528ppi :)
To me, the loophole seems to be 'Now his widow can sell those shares without paying any income tax on the appreciation before his death. She would have to pay taxes only on the increase in value from the time of his death to the time of the sale. '
Why doesn't the widow need to pay taxes on the increase from the original cost basis to time of sale? What is the reasoning for resetting the cost basis to 'value at time of death', when no taxes are paid at that time?
GWT takes the idea one step further - the code splitting functionality lets you define split points, and code that only ever gets called behind the split point does not need to be downloaded on page load, but can instead be downloaded when that split point is first reached.