From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] predefined classes
Date: Sun, 02 Jul 2017 11:51:04 -0700 [thread overview]
Message-ID: <8737ae4qqv.fsf@the-brannons.com> (raw)
In-Reply-To: <20170601205258.eklhad@comcast.net> (Karl Dahlke's message of "Sat, 01 Jul 2017 20:52:58 -0400")
Karl Dahlke <eklhad@comcast.net> 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
next prev parent reply other threads:[~2017-07-02 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 0:52 Karl Dahlke
2017-07-02 18:51 ` Chris Brannon [this message]
2017-07-03 11:48 ` 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=8737ae4qqv.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--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).