From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (75-164-214-250.ptld.qwest.net [75.164.214.250]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 2F4DC77B1A for ; Fri, 5 Dec 2014 13:53:55 -0800 (PST) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20141105062558.eklhad@comcast.net> <20141205185712.GI14122@toaster.adamthompson.me.uk> Date: Fri, 05 Dec 2014 13:52:12 -0800 In-Reply-To: <20141205185712.GI14122@toaster.adamthompson.me.uk> (Adam Thompson's message of "Fri, 5 Dec 2014 18:57:12 +0000") Message-ID: <87k325kbn7.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] V8 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 21:53:55 -0000 Adam Thompson 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. -- Chris