edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Engine
Date: Fri, 05 Dec 2014 05:59:21 -0500	[thread overview]
Message-ID: <20141105055921.eklhad@comcast.net> (raw)

Before we dive headlong into a redesign, it might be worth asking
whether there is a better engine out there.
After the 24 api, mozilla became very confusing, in my opinion.
Not because of c++, but because of all those compartments etc.
I think we got them right, but it is a house of cards.
Blow on it the wrong way and it collapses.
And I don't like its fixed js heap size, that's not very practical.
I've heard chrome is public domain.
Do they have a better, stand alone js engine,
and might they, or someone else, offer some dom support that we could use,
assuming it can be disentangled from the screen or other representations?
Even if we have to take the code and mangle it,
rather than using a clean library with a published api,
it still might be worth it.
A lot of code goes into a browser.
But if our approach, mozjs24 with a hand crafted dom on top,
turns out to be the best way, then I am willing to march on.

Karl Dahlke

                 reply	other threads:[~2014-12-05 11:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141105055921.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).