From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 69506787DC for ; Fri, 5 Dec 2014 03:01:03 -0800 (PST) Received: from resomta-ch2-11v.sys.comcast.net ([69.252.207.107]) by resqmta-ch2-09v.sys.comcast.net with comcast id PmzK1p0042Ka2Q501mzMLU; Fri, 05 Dec 2014 10:59:21 +0000 Received: from eklhad ([68.84.191.77]) by resomta-ch2-11v.sys.comcast.net with comcast id PmzM1p0071gep3001mzMPg; Fri, 05 Dec 2014 10:59:21 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Fri, 05 Dec 2014 05:59:21 -0500 Message-ID: <20141105055921.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417777161; bh=GPB1LQ4G7YBQoIUavi4JQViedZaH8Yggc15ETLiPxBg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=C99UMoewixAxRpCdvgdrf4mZdZaHduRurFeAnB6J/xMlaiPw+MmDQsmuP7lxVhuwE IF4sliFZuAMMQZi8FzopFHzsvKaHb9S0nxnid+YRjd+wooo3cfcloc9OR1YB848BKU f/6XdM/zSSP8Pe9saSvVoB2C+ktINXXa0/dmhI3nJ1TXejsOXXXpEwtbhaFt8cSvoT E/R9ibwvrFuTszRpRw4Gf7GrrQFbMm4Bv93KB/iETHzF4reFESJMqNdHahjkX6gkFZ l+SSjPDN6cjktQi4SioAmWNoBkw5umBqWp8cXhlh/L61reNMtggy+0z6+J2kPwTw2a b62JDfpbBMTDg== Subject: [Edbrowse-dev] Engine X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 11:01:03 -0000 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