Editing XPCOM (section)

==Past overuse==
XPCOM adds a lot of code for [[Marshalling (computer science)|marshalling]] objects, and in the [[Netscape]] era XPCOM was overused for internal interfaces where it wasn't truly necessary, resulting in [[software bloat]].<ref>{{cite web |url = https://arstechnica.com/information-technology/2004/06/collins-interview/2/ |title = Ars Technica sits down with Scott Collins from Mozilla.org |author = Jorge O. Castro |publisher = Ars Technica |date = 2004-06-15 |access-date=2017-02-16}}</ref> This was a key reason why in 2001 [[Apple Inc.|Apple]] forked [[KHTML]], not Gecko, to create the [[WebKit]] [[browser engine|engine]] for its [[Safari (web browser)|Safari]] browser.<ref>{{cite web|url=http://news.cnet.com/2100-1023-980492.html |archive-url=https://web.archive.org/web/20121025015655/http://news.cnet.com/2100-1023-980492.html |title=Apple snub stings Mozilla |author=Paul Festa |publisher=[[CNET Networks]] |date=2003-01-14 |archive-date=2012-10-25 |access-date=2017-02-16 |author-link=Paul Festa |url-status=dead }}</ref>

Mozilla has since cleaned up some of the XPCOM bloat.<ref>{{cite web | url= https://wiki.mozilla.org/Gecko:DeCOMtamination | title= Gecko:DeCOMtamination}}</ref> By 2008, this combined with other efforts resulted in big performance improvements for [[Gecko (software)|Gecko]].<ref>{{cite web |url =https://arstechnica.com/information-technology/2008/09/mozilla-committed-to-gecko/ |author = Ryan Paul |title = Why Mozilla is committed to Gecko as WebKit popularity grows |date = 2008-09-09 |access-date=2017-02-16}}</ref>
<!--Note: this section is NOT about add-on support, it's about core browser functionality. So don't add Firefox 57 or similar info here; that's already sufficiently covered in the lede.-->