3 ms·
You're talking about memory leaks as though they were a subjective thing (because nobody accused Chrome of having leaks, it doesn't). They are not. Objectively,
by pcwalton 13y ago
You're talking about memory leaks as though they were a subjective thing (because nobody accused Chrome of having leaks, it doesn't). They are not. Objectively, both Gecko and WebKit have leaks, as a search through the bug trackers of both projects will confirm. (IMO, Gecko's approach to dealing with leaks -- a cycle collector -- is a superior approach to WebKit's more ad-hoc approach.)
- thezilch 13y agoAs a developer, I couldn't possibly say with a straight face that a codebase like FF's or Chrome's, in size and language, are immune to leaks. I'm speaking about them the way every armchair developer has attacked FF over the years. I'm not saying they are right or wrong. I haven't invested myself in the issue, and I've stated or alluded to, several times, that it was not the "why" but the "what" that drove me. Firefox was slower and did less, so I switched. Anecdotal; 100% agree; I couldn't tell you exactly what I want; I don't necessarily have the time. For some, I'm sure the scale has dropped the opposite way (eg. they need more from FF's extension model).
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]