Re: [Edbrowse-dev] V8

[Adam Thompson <arthompson1990@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

On Fri, Dec 05, 2014 at 01:52:12PM -0800, Chris Brannon wrote:
> Adam Thompson <arthompson1990@gmail.com> writes:
> 
> > Tbh, having seen the way mozilla's api changes between releases,
> > making it a maintainability nightmare,
> > I'm ready to investigate another engine
> 
> I'm not convinced that V8 will solve this problem.  Gentoo
> stopped offering v8 as a standalone package some months ago, and if I
> remember correctly, the reason had something to do with the speed of
> development of both v8 and chromium.  So now they package v8 as part of
> chromium, in order to keep them in sync.
> My memory is fuzzy here, so I may be blowing smoke.
> But we need to take a very hard look at API stability before jumping
> ship.

That's interesting, I didn't know that.
The problem is that I suspect the next thing we'll probably need to do is
support mozjs 31 (whenever that's released)
and Mozilla publicly say that they've developed spidermonkey for use in firefox
and they can (and do) change the api frequently to keep up with the needs of
the firefox project. That's fine, but Debian's already on mozjs 26 (all be it
they're still packaging mozjs 24),
and I've seen a mozjs 31, and who knows what the api changes are like there.
I'm not saying v8's the answer, but we need to try and find something which we
can maintain, if only for the purposes of keeping up with security advisories etc.
In addition, it'd be beneficial if we could decouple the DOM from the js engine
we're currently using (which I know is slightly different to previous thinking)
since at the moment, changing engine's going to be a *lot* of work.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]