From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:af6e:e500::35bb:7ca9]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 72A037933B for ; Sun, 2 Jul 2017 11:50:37 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20170601205258.eklhad@comcast.net> Date: Sun, 02 Jul 2017 11:51:04 -0700 In-Reply-To: <20170601205258.eklhad@comcast.net> (Karl Dahlke's message of "Sat, 01 Jul 2017 20:52:58 -0400") Message-ID: <8737ae4qqv.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] predefined classes X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.24 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 18:50:37 -0000 Karl Dahlke writes: > It's also about 4 times as much code. > So I remain in the "implement it in js" camp, Let me strengthen your case just a little bit. Every couple years, we get forced to make some sweeping changes to the edbrowse JS code, on account of API deprecation. Here's a little summary of history since adopting Spidermonkey. You started with Spidermonkey JS 1.5. That was around for a while, but it was dropped circa 2011. We had to port to 1.8.5, the new hotness. In early 2014, 1.8.5 was on the chopping block, and we had to port to version 24. Now, version 24 is on the way out. We have to make more changes. This is all a bunch of churn. Nobody seems too thrilled. What is going to happen two to three years from now? I'm tentatively in your camp. Problem is, I see both sides of this argument, so I can't make a clear stand either way. -- Chris