> > A Electron-like project. I don't think there's anybody who would think > > that having a Electron-compatible tool based on gecko is a bad idea > > (we will likely go this route with Servo). I'm just not sure we have > > the resources to work on something like that *today* though. > I don't buy that. We just cancelled a bunch of projects and we still don't > have the resources? If that is really true then maybe we should be hiring > people.
Whatever happens, I really recommend that we build this on top of Spidermonkey + Rust. We can then have 2 separate implementations of BrowserWindow for Servo and Gecko. On Fri, Feb 26, 2016 at 7:16 PM, Benjamin Francis <[email protected]> wrote: > On 26 February 2016 at 17:55, Myk Melez <[email protected]> wrote: >> >> >> I'd like to see this too, if only because <webview> is more ergonomic and >> easier to distinguish from the existing <iframe mozbrowser> API. However, >> the isolated <iframe mozbrowser> from bug 1238160 is reasonable and a great >> start. > > > I agree, let's build on that. > >> >> I like this idea in theory. But I want to understand how it's different >> from Electron, besides simply using different underlying technology. In >> other words: what makes it unique that justifies the effort? > > > Why does it even have to be unique? Being able to build a browser using a > browser engine seems like table stakes to me... > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
