<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">
<blockquote style="border: 0px none;"
cite="mid:20180309002227.GV20510@kmag.localdomain" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:kmaglione@mozilla.com"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Kris Maglione</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">2018
March 8 at 16:22</span></font></div> </div></div>
<div style="color: rgb(144, 154, 164); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><br>Removing
XPCOM entirely is not really a possibility. Removing XPConnect
bindings entirely is... theoretically possible, but would be a
monumental
amount of work, and is not something I've heard anyone seriously
suggest.
<br></div>
</blockquote>
If we removed XPConnect bindings entirely and converted XPIDL interfaces
used only by C++ into concrete native classes, then what else would
continue to need XPCOM?<br>
<br>
-myk<br>
<br>
</body></html>