I don't think anyone would disagree with the reasons for doing this. I, like James who brought it up earlier, am concerned that we from the emails appear to think that implementing the wire protocol would be sufficient to making sure we have the same semantics.
As mentioned by Karl earlier, it was part of the Browser Testing Tools WG, but was dropped due to lack of interest from vendors but this thread is now suggesting that feeling has changed. I am happy, as chair, to see about adding it back when we recharter, which luckily at the end of September! I am happy to create a separate thread to get this started. David On 31 August 2017 at 21:51, Jim Blandy <jbla...@mozilla.com> wrote: > Sorry for the premature send. The complete message should read: > > The primary goals here are not related to automation and testing. > > - We want to migrate the Devtools console and the JS debugger to the CDP, > to replace an unpopular protocol with a more widely-used one. > > - Servo wants its devtools server to use an industry-standard protocol, not > Firefox's custom thing. > > - We'd like to have a devtools server we can share between Gecko and Servo. > > - We'd like to move devtools server code out of JS and into a language that > gives us better control over memory use and performance, because the > current server, implemented in JS, introduces a lot of noise into > measurements, affecting the quality of the performance data we're able to > collect. > > - We'd like to share front ends (i.e. clients) between Firefox and Servo. > devtools.html already implements both the Firefox protocol and the CDP. > > Using a protocol that's more familiar to web developers doing automation > and testing is also good, and we're hoping that will have ancillary > benefits. For example, it turns out that there is lots of interest in our > new JS debugger UI, which has hundreds of contributors now. I don't know > why people want a JS debugger UI, but they do. I believe that Firefox's use > of a bespoke protocol prevents many similar opportunities for > collaboration. > > > On Thu, Aug 31, 2017 at 1:36 PM, Jim Blandy <jbla...@mozilla.com> wrote: > > > Certain bits of the original post are getting more emphasis than I had > > anticipated. Let me try to clarify why we in Devtools want this change or > > something like it. > > > > The primary goals here are not related to automation and testing. They > are: > > > > - to allow Devtools to migrate the console and the JS debugger to the > > CDP; > > - to start a tools server that can be shared between Gecko and Servo; > > - to replace Gecko's devtools server, implemented in JS, with one > > implemented in Rust, to reduce memory consumption and introduce less > noise > > into performance and memory measurements > > > > > > > > and to help us share code with Servo. Our user interfaces already work > > with the CDP. > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
