3 ms·
All I said was that the code can't be copied and pasted between browsers. (probably.) Doing so A. wont work (most likely), and B. lead to poor memory managemen
by Zev 18y ago
All I said was that the code can't be copied and pasted between browsers. (probably.) Doing so A. wont work (most likely), and B. lead to poor memory management on the application if it somehow does manage to work.
Instead, the ideas will be taken and copied (and hopefully made better). But idea's aren't code. So unless you're talking about human memory (which seems highly unlikely given you said "…where Firefox can improve") I'm not quite sure what benefits in terms of memory usage Firefox (or Safari or even Opera) gets from this.
- stcredzero 18y agoEntire subsystems like Google Gears can probably be put in place, with a lot of code used without modification. Also, if someone implemented my original proposal in this thread, this would be entirely orthogonal to any code currently in Firefox.
- DougBTX 18y agoGears and WebKit were designed to be reusable, other features such as the process model would be much harder to integrate into Firefox. I'd be interested to see Firefox embedded in a "wrapper" VM, but I think you'll find it harder to implement than you expect. Please post to HN if you give it a shot.