From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] obj = new Foo()
Date: Wed, 05 Jul 2017 08:01:12 -0700 [thread overview]
Message-ID: <87bmozyll3.fsf@the-brannons.com> (raw)
In-Reply-To: <20170605095053.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 05 Jul 2017 09:50:53 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> If we get duktape working, and if jsrt passes, and it meets our needs, I don't think we'll ever go back to mozilla.
> I can't imagine going back to mozilla.
I can't imagine a really compelling reason to switch again, either.
> but if you-all can convince me that's a bad idea, then I guess I could
> leave a bunch of classes in C, where they are now, even though they're
> pure and simple and could easily be in js instead.
The main arguments for and against moving classes into JS have already
been made on this list. And if we ever do have to switch away from
Duktape for some reason, that switch is going to be painful,
regardless of whether the code is in C or JS.
So I don't think I can convince you.
-- Chris
next prev parent reply other threads:[~2017-07-05 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 13:50 Karl Dahlke
2017-07-05 15:01 ` Chris Brannon [this message]
2017-07-05 21:13 ` Kevin Carhart
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=87bmozyll3.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).