Hi,
2013/1/14 Rob Campbell <[email protected]> > If interoperability ever does become a concern (we want to debug chrome > through the Firefox debugger for example), I think the concern is a bit different than that. An interoperable protocole will allow web developers to use third party tools that will allow them to debug both Chrome and Firefox (and any browser that will implement it) at the same time. I think about IDE or extensible text editors (such as Vim or Sublime Text). Everything that could help web developer to be more productive will be blessed. It's not just about having nice tools inside the browsers, it's also the ability to plug them to other tools. This is especially true in the mobile world where it is not possible (or it's very difficult) to access directly to the browser. As an example, I love Adobe Edge Inspect (http://html.adobe.com/edge/inspect/) that prevent ours of work on mobile WebKit browsers. The interoperability on such subjects is a key factor to see the "Web as a platform" becoming something more than a simple marketing buzz word. > we could probably implement a protocol translation layer to talk to a > foreign browser / debugger server. That way we could keep the nice features > of our protocol and still have the capability to talk to other browsers. > And vice versa. We'd also not have to rewrite our debugger's innards from > scratch. > > That might be a fun summer of code project. > That sounds like a great idea :D Best, -- Jeremie ............................. Web : http://jeremie.patonnier.net Twitter : @JeremiePat <http://twitter.com/JeremiePat> _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
