The issue/problem is that you have to actually pay the developers/managers/staff working in/on/around Chrome the browser and OS somehow. Any monetization strate

The issue/problem is that you have to actually pay the developers/managers/staff working in/on/around Chrome the browser and OS somehow. Any monetization strategy will lead to conflicts of interest and poor decisions along the way. For example, adspace is the biggest offender in terms of cripling browser resource overload. If they implemented, say a 500kb cap for JS in IFRAME, and disabled JS entirely for IFrames more than two layers in HTML>IFRAME>IFRAME get JS, another layer doesn't... that would be a massive boost to actual performance, especially in low-resource devices. Unfortunately, such limitations will NEVER be implemented by Google, and Firefox getting most of their funding from Google as well won't do it. MS might, but I don't see them making those kinds of changes in their fork. Even as a separate entity, Chrome would have to get funding from somewhere. Also, where would ChromeOS fall, or Android? What would stop Google from forking and starting all over again?