<div>Absolutely. There are lots of things that can be parallelized here. Some of the work is obvious, as you point out: redoing basic presentations from XUL to HTML. Figuring out where HTML5 isn't up to the task can be done alongside that work, and we can propose new standards to add the stuff we need to take those next steps.<br><br>Sheppy<br><br></div>
<div class="gmail_quote">_____________________________<br>From: Gijs Kruitbosch <<a href="mailto:gijskruitbosch@gmail.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="0">gijskruitbosch@gmail.com</a>><br>Sent: Thursday, July 16, 2015 5:18 PM<br>Subject: Re: Living in a Go Faster, post-XUL world<br>To: Eric Shepherd <<a href="mailto:eshepherd@mozilla.com" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="3">eshepherd@mozilla.com</a>><br>Cc: Firefox Dev <<a href="mailto:firefox-dev@mozilla.org" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="4">firefox-dev@mozilla.org</a>><br><br><br> <div dir="ltr"> <div> Converting our in-content pages, converting our web-facing XBL (video controls come to mind), investigating more or less orthogonal perf improvements for startup (potentially by replacing some bits of XUL with HTML in the main window, but maybe through other means), improving "new" CSS flexbox performance, making an inventory of "XUL things" that we rely on right now that don't have HTML equivalents (XUL persistence, window attributes that get reflected to native code, certain -moz-appearance values, layout for panels/popups where the bounds are determined by the page instead of the bounds being determined for the page, maybe other stuff...) and figuring out paths to replace those, expanding exposed APIs (like e.g. CustomizableUI) to accommodate other things that add-ons currently do with XUL overlays (e.g. "load script X in every browser window", "add menu Y in the Tools menu", "add fancy toolbaritem (not a button) <whatever>" to the set of customizable toolbar items... etc. <br> <br> </div> <div> All of these can be worked on more or less in parallel. There's probably other things that I've forgotten about. <br> </div> <div> <br> </div>~ Gijs <br> </div> <div class="gmail_extra"> <br> <div class="gmail_quote"> On 16 July 2015 at 22:07, Eric Shepherd <span dir="ltr"><<a href="mailto:eshepherd@mozilla.com">eshepherd@mozilla.com</a>></span> wrote: <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div bgcolor="#FFFFFF"> <span class=""><span>David Rajchenbach-Teller wrote:</span><br> <blockquote> <pre>P.S.: I can clarify "finite" as "finished long, long before we switch toServo", if you prefer.</pre> </blockquote></span> That helps... a little. :) <br> <br> I think it's clear (I *hope* it is, anyway) that we need to find ways to do this iteratively, instead of it having to be a single huge, monolithic project that will essentially never be finished. <br> <br> Figuring out what those iterations are is the trick. <span class=""><br> <br> <div> -- <br> <br> <span style="font-weight:bold">Eric Shepherd</span> <br> <span style="font-weight:bold">Senior Technical Writer</span> <br> <a href="https://www.mozilla.org/">Mozilla</a> <br> Blog: <a href="http://www.bitstampede.com/">http://www.bitstampede.com/</a> <br> Twitter: <a href="http://twitter.com/sheppy">http://twitter.com/sheppy</a> <br> <a style="font-style:italic" href="https://freebusy.io/eshepherd@mozilla.com">Check my Availability</a> <br> </div> </span> </div> <br>_______________________________________________ <br> firefox-dev mailing list <br> <a href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a> <br> <a href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a> <br> <br> </blockquote> </div> <br> </div> <br><br></div>