From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] V8
Date: Fri, 5 Dec 2014 18:57:12 +0000 [thread overview]
Message-ID: <20141205185712.GI14122@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20141105062558.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Fri, Dec 05, 2014 at 06:25:58AM -0500, Karl Dahlke wrote:
> After about ten minutes of reading, I'm almost convinced
> we should switch to v8.
> https://developers.google.com/v8/intro
> The api just has to be cleaner than mozilla (he said somewhat on faith),
> and there's an entire public domain dom on top of it in google chrome,
> that we might be able to pilfer.
> I was about to step through the download and build process,
> just so I could play with it, but on a whim I typed in
> yum install v8
> and here it comes, packaged with fedora 20.
> Very likely it is available on your distro too.
> So that saves us a few hours work and hassle,
> and makes the path all the more plausible.
Yeah, on debian I think there's a package,
I'll install and play with it over the weekend.
Tbh, having seen the way mozilla's api changes between releases,
making it a maintainability nightmare,
I'm ready to investigate another engine (I'd thought of v8 before but couldn't
find a Debian package for it and didn't want to do the work myself).
I'll also have a look at the api to see if it's worth changing.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-05 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 11:25 Karl Dahlke
2014-12-05 18:57 ` Adam Thompson [this message]
2014-12-05 21:52 ` Chris Brannon
2014-12-05 22:14 ` Adam Thompson
2014-12-05 19:05 Karl Dahlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141205185712.GI14122@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).